Bump master bootstrap compiler

[pietroalbini]

This PR bumps the bootstrap compiler to the beta created earlier this week, cherry-picks the stabilization version number updates, and updates the cfg(bootstrap)s.

r? @Mark-Simulacrum

[rustbot]

Hey! It looks like you've submitted a new PR for the library teams!

If this PR contains changes to any rust-lang/rust public library APIs then please comment with @rustbot label +T-libs-api -T-libs to tag it appropriately. If this PR contains changes to any unstable APIs please edit the PR description to add a link to the relevant API Change Proposal or create one if you haven't already. If you're unsure where your change falls no worries, just leave it as is and the reviewer will take a look and make a decision to forward on if necessary.

Examples of T-libs-api changes:

• Stabilizing library features
• Introducing insta-stable changes such as new implementations of existing stable traits on existing stable types
• Introducing new or changing existing unstable library APIs (excluding permanently unstable features / features without a tracking issue)
• Changing public documentation in ways that create new stability guarantees
• Changing observable runtime behavior of library APIs

[Noratrieb]

@Swatinem can the entire function be removed now?

[pietroalbini]

Removed the unknown lang items for now, IMO it's fine to merge this if it builds and cleanup the functions (if needed) later.

[Swatinem]

Yes, the idea was that this whole function can be removed now, as it is now unused.

[Mark-Simulacrum]

Happy to see a separate PR with more expansive cleanup, but I think minimal work as part of this PR is best.

[Mark-Simulacrum]

r=me modulo CI

[pietroalbini]

@bors r=Mark-Simulacrum p=1

[bors]

📌 Commit 8c30ada576d7ef079c666e6ff7f07b492f8359a3 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[bors]

⌛ Testing commit 8c30ada576d7ef079c666e6ff7f07b492f8359a3 with merge a3fd12238cca733fe3e05880c2d13ab942af30bf...

[bors]

💔 Test failed - checks-actions

[pietroalbini]

@bors r=Mark-Simulacrum

[bors]

📌 Commit 0191c5e13dc865e270741be2c942e58f75ebfbfb has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[bors]

⌛ Testing commit 0191c5e13dc865e270741be2c942e58f75ebfbfb with merge 9cc6ef7298ac57aa15ddfd8c444a24f395fd691a...

[bors]

💔 Test failed - checks-actions

[bors]

⌛ Testing commit fbe0450 with merge 0354138d267a6b4e3191a8b91bbd5e67df1455f5...

[bors]

💔 Test failed - checks-actions

[lqd]

Apparently #105800 is still not enough to make rust.lto = thin work at stage0. Maybe we can take care of this later and not remove this cfg(bootstrap) for now ?

[lukas-code]

Stage0 LTO seems to be fixed with this patch. I have no idea if that makes sense though, and it might be better to just disable stage0 LTO, because it takes forever for little benefit.

diff --git a/src/bootstrap/compile.rs b/src/bootstrap/compile.rs
index ae5dfdea19f..c8aa8c99163 100644
--- a/src/bootstrap/compile.rs
+++ b/src/bootstrap/compile.rs
@@ -362,12 +362,7 @@ pub fn std_cargo(builder: &Builder<'_>, target: TargetSelection, stage: u32, car
     // built with bitcode so that the produced rlibs can be used for both LTO
     // builds (which use bitcode) and non-LTO builds (which use object code).
     // So we override the override here!
-    //
-    // But we don't bother for the stage 0 compiler because it's never used
-    // with LTO.
-    if stage >= 1 {
-        cargo.rustflag("-Cembed-bitcode=yes");
-    }
+    cargo.rustflag("-Cembed-bitcode=yes");
 
     // By default, rustc does not include unwind tables unless they are required
     // for a particular target. They are not required by RISC-V targets, but

[Mark-Simulacrum]

Restored the gate on stage 0, but also dropped an explicit cfg(bootstrap) in the comment. I'm not sure we actually want cfg(bootstrap) there -- doing LTO in stage 0 doesn't feel very helpful.

@bors r+ rollup=never

[bors]

📌 Commit cc4e434 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[bors]

⌛ Testing commit cc4e434 with merge b15ca66...

[bors]

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing b15ca66 to master...

[rust-timer]

Finished benchmarking commit (b15ca66): comparison URL.

Overall result: ❌ regressions - ACTION NEEDED

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	2.7%	[1.3%, 4.2%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	2.3%	[2.3%, 2.3%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.6%	[-2.6%, -2.6%]	1
All ❌✅ (primary)	-	-	0

Cycles

This benchmark run did not return any relevant results for this metric.

[Mark-Simulacrum]

These benchmarks are historically prone to noise and this change is required regardless.

[lqd]

both benchmarks have even already reverted back to their steady-state by now