-
Notifications
You must be signed in to change notification settings - Fork 13k
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
store codegen_fn_attrs
in crate metadata
#96473
Conversation
r? @fee1-dead (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 00da420d86e9c4c61da6aa3f22f3d853aa971794 with merge 8bda55c77d599ffd1ee91eba6c0dfa8d31734149... |
☀️ Try build successful - checks-actions |
Queued 8bda55c77d599ffd1ee91eba6c0dfa8d31734149 with parent bb85bca, future comparison URL. |
Finished benchmarking commit (8bda55c77d599ffd1ee91eba6c0dfa8d31734149): comparison url. Summary:
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 may lead 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 Footnotes |
maybe caching it on disk if its already simply pulled from the metadata isn't too useful @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit de08cbe2840ae1761852a1a984627c82640b605e with merge 95de7c6d4d85ca601c2838decc62bacf341ca265... |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
☀️ Try build successful - checks-actions |
Queued 95de7c6d4d85ca601c2838decc62bacf341ca265 with parent bb85bca, future comparison URL. |
Finished benchmarking commit (95de7c6d4d85ca601c2838decc62bacf341ca265): comparison url. Summary:
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 may lead 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 Footnotes |
alright, this performance decrease seems acceptable, considering that with #95562 we can now remove |
r? rust-lang/compiler |
Normally, I'd be all for more queries, but the perf result is a bit too large for it's own good. It looks like it is dominated by metadata encoding. It may be more interesting to land the refactoring in #95562 that makes it possible to omit attributes. |
9fa5d1e
to
9dc70c0
Compare
@rustbot ready |
Improved all, except doc builds (if uncheck all profiles except doc, it can be clearly visible), which regressed. |
r=me with the warning removed. |
9dc70c0
to
32b13ac
Compare
@bors r=cjgillot |
📌 Commit 32b13ac has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (88860d5): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
Fix outdated comment of `fn_can_unwind` The first part is outdated since rust-lang#96473, and the second part is outdated since rust-lang#97235
extracted from #95562 because the change isn't trivial.