[beta] backports - #162987
[beta] backports#162987
Conversation
(cherry picked from commit dad850c)
This is done just in case we want to later do stuff like adding a `Sized` supertrait. See discussion at https://rust-lang.zulipchat.com/#narrow/channel/219381-t-libs/topic/Should.20.60VaArgSafe.60.20require.20.60Sized.60.3F/with/622074620 (cherry picked from commit 16529d7)
This PR does a "breaking" change on API that's stabilized in 1.99.0 beta, but has not reached stable yet, so we can make this change. H th is PR will need a beta backport. (cherry picked from commit 246105d)
(cherry picked from commit 5e3ad00)
|
@bors r+ rollup=never |
|
If you're doing backports nowish, mind reviewing #162820? I think it should be fine but also am not too familiar with the process. (They could probably actually be rolled up together) |
(cherry picked from commit 37aaf5c)
This is a rather old config, added in c924aed0b9ac ("Fix Armv8-M
Baseline compilation"). `thumb_1` is somewhat misleading, since targets
with `thumb2` also support basic `thumb` instructions. Rename it to be
more clear about what this is actually checking.
The config is not currently used but may be in the future.
(cherry picked from commit 5c59263)
We still match on target name because we can't always rely on config from the unstable `arm_target_feature`. However, we can still assert that things match up when running in the compiler-builtins CI. This is disabled for now because it fails on three thumb targets: * thumbv4t-none-eabi * thumbv5te-none-eabi * thumbv6-none-eabi This will be resolved in a future commit. Checking for the verbose build is a good indicator that we are in our CI, rather than any other that might set the `CI` env. (cherry picked from commit 9e5d248)
Fixes: rust-lang#162259 (cherry picked from commit a7f33f3)
(cherry picked from commit 192ea4f)
|
This pull request was unapproved. |
|
@bors r+ |
|
Scheduling: Bump this above other stuff, since beta is a ticking clock. @bors p=6 |
This comment has been minimized.
This comment has been minimized.
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
So close
@bors retry |
|
❗ You can only retry pull requests that are approved and have a previously failed auto build. Hint: There is currently a pending auto build on this PR. To cancel it, run |
|
💔 Test for c033dd8 failed: CI. Failed job:
|
|
@bors retry |
This comment has been minimized.
This comment has been minimized.
|
💔 Test for b43b933 failed: CI. Failed job:
|
|
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot) |
|
@bors retry spurious |
core::fmt::NumBufferinalloc(andstd) Re-exportcore::fmt::NumBufferinalloc(andstd) #161430VaArgSafedyn-incompatible MakeVaArgSafedyn-incompatible #162374VaArgSafeDestabilizeVaArgSafe#162909r? me