-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Stage0 bootstrap update #140887
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
base: master
Are you sure you want to change the base?
Stage0 bootstrap update #140887
Conversation
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt Some changes occurred to the CTFE machinery Some changes occurred in compiler/rustc_attr_data_structures Some changes occurred in library/core/src/fmt/rt.rs cc @m-ou-se This PR changes how LLVM is built. Consider updating src/bootstrap/download-ci-llvm-stamp. Some changes occurred in compiler/rustc_sanitizers cc @rcvalle Some changes occurred in compiler/rustc_codegen_ssa Some changes occurred to the intrinsics. Make sure the CTFE / Miri interpreter cc @rust-lang/miri, @RalfJung, @oli-obk, @lcnr Some changes occurred in compiler/rustc_attr_parsing rust-analyzer is developed in its own repository. If possible, consider making this change to rust-lang/rust-analyzer instead. cc @rust-lang/rust-analyzer This PR modifies If appropriate, please update Some changes occurred to the platform-builtins intrinsics. Make sure the cc @antoyo, @GuillaumeGomez, @bjorn3, @calebzulawski, @programmerjake |
The job Click to see the possible cause of the failure (guessed by this bot)
|
also @zetanumbers @petrochenkov since you were also involved with async drop. for some reason there is an ICE when compiling the standard library after the bootstrap bump, could you take a look at it? ideally there's some small bugfix that can be backported to beta |
Minimized repro, in case it helps: #140423 (comment) |
On mobile for the next 6h, so I cant provide PRs, but just early return from the async mir shim code to produce a dummy mir body. Not dropping anything isn't worse than before the PR and we'll fix it on nightly again. No stable code is affected by essentially disabling the feature on beta |
I'd say the code is sound, as a |
you can take the fix from #140902 it's hacky but it does the job with no risk and we'll fix it cleanly on master |
Prepared the backport PR. |
This PR follows the release process to update the stage0 compiler.
The only thing of note is 58651d1, which was flagged by clippy as a correctness fix. I think allowing that lint in our case makes sense, but it's worth to have a second pair of eyes on it.
r? @Mark-Simulacrum