-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Reduce use of LocalDefId <-> HirId maps #90146
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 437652f1641a199a4822f756bf3ce86f7bbfea49 with merge ba6244813e20a79c9f865108e1add3078beb8799... |
☀️ Try build successful - checks-actions |
Queued ba6244813e20a79c9f865108e1add3078beb8799 with parent 45b600c, future comparison URL. |
Finished benchmarking commit (ba6244813e20a79c9f865108e1add3078beb8799): comparison url. Summary: This change led to large relevant mixed results 🤷 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never |
This comment has been minimized.
This comment has been minimized.
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 6f4cc96 with merge 3c98d5fc58ff609ab72025df0586f8e61b4f96b1... |
☀️ Try build successful - checks-actions |
Queued 3c98d5fc58ff609ab72025df0586f8e61b4f96b1 with parent dd757b9, future comparison URL. |
Finished benchmarking commit (3c98d5fc58ff609ab72025df0586f8e61b4f96b1): comparison url. Summary: This change led to large relevant mixed results 🤷 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never |
☔ The latest upstream changes (presumably #91230) made this pull request unmergeable. Please resolve the merge conflicts. |
☔ The latest upstream changes (presumably #90639) made this pull request unmergeable. Please resolve the merge conflicts. |
I'm happy to r=me this. Please rebase and squash the history a little before merging though. |
@bors r=nagisa |
📌 Commit 8617ff0 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (f9d61cd): 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. @rustbot label: -perf-regression |
This is an attempt to reduce the perf effect of #89278.
r? @ghost