-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Cache expansion hash globally #87044
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 5b0308c7296209d4632a80282e6e1c8d9609ce1e with merge 67224bcd833f32325793fec7ff8d021b84edd6d5... |
☀️ Try build successful - checks-actions |
Queued 67224bcd833f32325793fec7ff8d021b84edd6d5 with parent 432e145, future comparison URL. |
Finished benchmarking try commit (67224bcd833f32325793fec7ff8d021b84edd6d5): comparison url. Summary: This change led to significant 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 perf run, please indicate this with @bors rollup=never |
LGTM, left some comments, mostly about readability/searchability. |
Three remaining questions about passing heavy structures by value - #87044 (comment), #87044 (comment), #87044 (comment). |
r=me with commits starting from c683196 squashed. |
@bors r=petrochenkov |
📌 Commit 616ce3c has been approved by |
The perf results are globally green with ~1% improvements, except an isolated regression on |
☀️ Test successful - checks-actions |
... instead of computing it multiple times.
Split from #86676
r? @petrochenkov