-
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
Remove eval_always from upvars. #90580
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 04f011f with merge 796a165526fe64e10911120021887580be2e8731... |
☀️ Try build successful - checks-actions |
Queued 796a165526fe64e10911120021887580be2e8731 with parent 4961b10, future comparison URL. |
Finished benchmarking commit (796a165526fe64e10911120021887580be2e8731): comparison url. Summary: This change led to moderate relevant improvements 🎉 in compiler performance.
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. @bors rollup=never |
LGTM. Let's do another perf run to make sure that nothing has changed since this was opened. @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 04f011f with merge d3ded1aef71b39954ec4b4fc7cfbfb2218d2bf82... |
☀️ Try build successful - checks-actions |
Queued d3ded1aef71b39954ec4b4fc7cfbfb2218d2bf82 with parent 883a241, future comparison URL. |
Finished benchmarking commit (d3ded1aef71b39954ec4b4fc7cfbfb2218d2bf82): comparison url. Summary: This change led to moderate relevant improvements 🎉 in compiler performance.
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. @bors rollup=never |
@bors r+ |
📌 Commit 04f011f has been approved by |
⌛ Testing commit 04f011f with merge b4b291a760dafc020b28e61ef835fe1d7ee5478f... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry |
⌛ Testing commit 04f011f with merge f5e758494b90eb33bff1759ddd9cc062d260348c... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (dd549dc): comparison url. Summary: This change led to small relevant improvements 🎉 in compiler performance.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Split off #86056
r? @ghost