-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Bump stage0 compiler to 1.56 #88752
Bump stage0 compiler to 1.56 #88752
Conversation
Yess, time to bump the compiler and library to @bors r+ |
📌 Commit 1bbb74cf695e9b0f8b80374b83e98ec66ed001d9 has been approved by |
1bbb74c
to
b6976a2
Compare
@bors r=m-ou-se |
📌 Commit b6976a213e43f100f1b50a306b6773be2c66afc5 has been approved by |
Also looks good to me! |
This comment has been minimized.
This comment has been minimized.
b6976a2
to
3ad6e84
Compare
@bors r=m-ou-se p=1 |
📌 Commit 3ad6e84faa5c6abbe88131384a8a64ee37f18218 has been approved by |
This comment has been minimized.
This comment has been minimized.
3ad6e84
to
b4e7649
Compare
@bors r=m-ou-se p=1 |
📌 Commit b4e7649 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (c5cbf78): comparison url. Summary: This change led to moderate relevant mixed results 🤷 in compiler performance.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression |
The regressions are pretty small, and scattered in +/- about equally. This PR also at least in theory doesn't change the compiler or standard library being benchmarked, so the differences are likely due to "noise" (presumably related to changes to the memory layout or something similar). @rustbot label: +perf-regression-triaged |
r? @pietroalbini (but others should feel free to steal)