-
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
[WIP] rustc_metadata: Switch each_child_of_item
from callback to iterator
#92251
Conversation
r? @jackh726 (rust-highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit b738128c6398f4751333ed9acd5e79d11763e1ad with merge c11423e489f70294eb5ece1e027fc8e9b0c376ec... |
☀️ Try build successful - checks-actions |
Queued c11423e489f70294eb5ece1e027fc8e9b0c376ec with parent 59337cd, future comparison URL. |
Finished benchmarking commit (c11423e489f70294eb5ece1e027fc8e9b0c376ec): comparison url. Summary: This change led to very large relevant regressions 😿 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 |
I've seen edge cases when |
to avoid allocations.
b738128
to
7bd38c9
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 7bd38c9 with merge de48e65ece49a289d7202477e406fd727029f15a... |
☀️ Try build successful - checks-actions |
Queued de48e65ece49a289d7202477e406fd727029f15a with parent d981633, future comparison URL. |
Finished benchmarking commit (de48e65ece49a289d7202477e406fd727029f15a): comparison url. Summary: This benchmark run shows 47 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 |
Let me know when this is ready for review. |
Looks like it's still not an improvement. |
to avoid allocations.