add c_variadic_experimental_arch feature#155974
add c_variadic_experimental_arch feature#155974folkertdev wants to merge 1 commit intorust-lang:mainfrom
c_variadic_experimental_arch feature#155974Conversation
This comment has been minimized.
This comment has been minimized.
531be28 to
c5b7925
Compare
|
This looks reasonable to me, based on the discussions in the lang meeting. We can always un-gate any of these targets in the future, when a maintainer of the target takes a close look and makes sure the tests pass. I think it might be useful to point people to an invocation of r=me with such a comment added next to the match arm for the unstable targets. (Not next to the match arm for RISC-V ILP32E, that one is unstable for a different reason.) @bors delegate+ |
|
✌️ @folkertdev, you can now approve this pull request! If @joshtriplett told you to " |
c5b7925 to
41796ec
Compare
|
r? joshtriplett |
|
|
|
These commits modify compiler targets. |
|
@bors r=joshtriplett |
…-arch, r=joshtriplett add `c_variadic_experimental_arch` feature tracking issue: rust-lang#155973 Based on https://hackmd.io/pIbUgMQuQcGaibJcinOcEw#Stabilize-c-variadic-function-definitions-rust155697, we'll gate niche targets where we don't control the implementation of `va_arg`, the ABI is unclear, or in general where we're not confident stabilizing the implementation.
Rollup of 6 pull requests Successful merges: - #155853 (Use `_mcount` as the mcount symbol name on RISC-V Linux GNU targets) - #155939 (Add feature gate for view_types experiment) - #155974 (add `c_variadic_experimental_arch` feature) - #155523 (Reorganize `tests/ui/issues/` - 02) - #155980 (Move `feature*` methods from `parse` mod to `errors` mod.) - #155987 (Make lifting infallible) Failed merges: - #155237 (Disentangle AST crates and error crates)
…-arch, r=joshtriplett add `c_variadic_experimental_arch` feature tracking issue: rust-lang#155973 Based on https://hackmd.io/pIbUgMQuQcGaibJcinOcEw#Stabilize-c-variadic-function-definitions-rust155697, we'll gate niche targets where we don't control the implementation of `va_arg`, the ABI is unclear, or in general where we're not confident stabilizing the implementation.
…uwer Rollup of 13 pull requests Successful merges: - #155249 (Fix: On wasm targets, call `panic_in_cleanup` if panic occurs in cleanup) - #155853 (Use `_mcount` as the mcount symbol name on RISC-V Linux GNU targets) - #155919 (simplify `ast_fragments!`) - #155939 (Add feature gate for view_types experiment) - #155974 (add `c_variadic_experimental_arch` feature) - #155991 (Catch unwinds from the global ctxt callback to complete queries profiling data in more cases) - #156003 (Pass Session to optimize_and_codegen_fat_lto) - #153566 (Add suggestion for E0401 on inner const items) - #154610 (Suggest public re-exports when a private module makes an import path inaccessible) - #155523 (Reorganize `tests/ui/issues/` - 02) - #155980 (Move `feature*` methods from `parse` mod to `errors` mod.) - #155987 (Make lifting infallible) - #155988 (tests/run-make/print-cfg: add Android target_env case)
tracking issue: #155973
Based on https://hackmd.io/pIbUgMQuQcGaibJcinOcEw#Stabilize-c-variadic-function-definitions-rust155697, we'll gate niche targets where we don't control the implementation of
va_arg, the ABI is unclear, or in general where we're not confident stabilizing the implementation.