-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
[perf only] revert conditional opt attributes #94439
Conversation
This comment has been minimized.
This comment has been minimized.
7794fad
to
5c0a848
Compare
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 5c0a848 with merge f417bb4942b44b9b830f944a05b3ff6f7bb252c2... |
☀️ Try build successful - checks-actions |
Queued f417bb4942b44b9b830f944a05b3ff6f7bb252c2 with parent ec0ab61, future comparison URL. |
Finished benchmarking commit (f417bb4942b44b9b830f944a05b3ff6f7bb252c2): comparison url. Summary: This benchmark run shows 32 relevant regressions 😿 to instruction counts.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never |
Not for merge.
This effectively reverts #94127. (Without fixing tests, so the test failure is expected.)
I want to see what the effect of #94127 would've been after #94221, which changed how we add attributes.
r? @ghost