-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
Stabilize extended_varargs_abi_support
#116161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
r? @wesleywiser (rustbot has picked a reviewer for you, use r? to override) |
|
@rustbot label F-extended_varargs_abi_support |
This comment has been minimized.
This comment has been minimized.
| (accepted, extended_key_value_attributes, "1.54.0", Some(78835), None), | ||
| /// Allows using `efiapi`, `aapcs`, `sysv64` and `win64` as calling | ||
| /// convention for functions with varargs. | ||
| (accepted, extended_varargs_abi_support, "1.65.0", Some(100189), None), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use CURRENT_RUSTC_VERSION instead of a version number here
|
Tracking issue: #100189 |
|
☔ The latest upstream changes (presumably #116550) made this pull request unmergeable. Please resolve the merge conflicts. |
|
☔ The latest upstream changes (presumably #118823) made this pull request unmergeable. Please resolve the merge conflicts. |
|
r? compiler |
|
I'm on vacation for a few days :) |
|
Not completely sure which team should be nominated for stabilization, so labeling both in doubt. |
|
Just to add on to @cjgillot 's comment above: @wesleywiser and I could not remember earlier today whether T-lang wants to own FCP'ing changes like this that are restricted to extending the set of calling-conventions (i.e. the (My own gut reaction is that T-compiler is a more natural owner for this than T-lang, but I wasn't certain and so it seems best to let the nomination stand and let the two teams duke it out.) |
|
Removing the T-compiler nomination until after T-lang discussed this. Feel free to re-add T-compiler! @rustbot label -I-compiler-nominated |
Rollup of 10 pull requests Successful merges: - rust-lang#116161 (Stabilize `extended_varargs_abi_support`) - rust-lang#132750 ([AIX] handle libunwind native_libs) - rust-lang#133488 (tests: Add regression test for self referential structs with cow as last field) - rust-lang#133569 (Bump `ruzstd` to 0.7.3) - rust-lang#133585 (Do not call `extern_crate` on current trait on crate mismatch errors) - rust-lang#133587 (Fix target_feature handling in freg of LoongArch inline assembly) - rust-lang#133599 (Add `+forced-atomics` feature to esp32s2 no_std target) - rust-lang#133620 (Simplify hir_typeck_pass_to_variadic_function) - rust-lang#133623 (Improve span handling in `parse_expr_bottom`.) - rust-lang#133625 (custom MIR: add doc comment for debuginfo) r? `@ghost` `@rustbot` modify labels: rollup
Rollup of 10 pull requests Successful merges: - rust-lang#116161 (Stabilize `extended_varargs_abi_support`) - rust-lang#132750 ([AIX] handle libunwind native_libs) - rust-lang#133488 (tests: Add regression test for self referential structs with cow as last field) - rust-lang#133569 (Bump `ruzstd` to 0.7.3) - rust-lang#133585 (Do not call `extern_crate` on current trait on crate mismatch errors) - rust-lang#133587 (Fix target_feature handling in freg of LoongArch inline assembly) - rust-lang#133599 (Add `+forced-atomics` feature to esp32s2 no_std target) - rust-lang#133620 (Simplify hir_typeck_pass_to_variadic_function) - rust-lang#133623 (Improve span handling in `parse_expr_bottom`.) - rust-lang#133625 (custom MIR: add doc comment for debuginfo) r? `@ghost` `@rustbot` modify labels: rollup
|
This is in beta but not yet stable. It should probably be reverted as https://godbolt.org/z/fYzxa8xW5 compiles with this but probably ought not to, at least on targets like i686-pc-windows-msvc where the underlying abi of |
|
@rustbot label +I-compiler-nominated +I-lang-nominated Should this be reverted (and backported) to allow addressing whether |
|
moving that discussion to a new issue. |
I think that is everything? If there is any documentation regarding
externand/or varargs to correct, let me know, some quick greps suggest that there might be none.Tracking issue: #100189