-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Query-ify needs_gdb_debug_scripts_section #81056
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion. |
⌛ Trying commit ecde548133cec4a4a8ca0b1c9ff382abc44cfcd5 with merge a3c8e320ca13e4cc1253c85b7cfbaf98a455560f... |
☀️ Try build successful - checks-actions |
Queued a3c8e320ca13e4cc1253c85b7cfbaf98a455560f with parent bc39d4d, future comparison URL. @rustbot label: +S-waiting-on-perf |
Finished benchmarking try commit (a3c8e320ca13e4cc1253c85b7cfbaf98a455560f): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
ecde548
to
aa6b566
Compare
r? @estebank |
☔ The latest upstream changes (presumably #81660) made this pull request unmergeable. Please resolve the merge conflicts. |
This ensures that a codegen unit DepNode does not have a direct dependency on the crate's attributes
aa6b566
to
3667b1d
Compare
Avoid a hir access inside get_static Together with rust-lang#81056 this ensures that the codegen unit DepNode doesn't have a direct dependency on any part of the hir.
@estebank Are there any changes that you'd like me to make? |
PR #79519 may have reduced the need for this: @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 3667b1d with merge c071c3594f1d95ba283af8252d803e1b74690fe0... |
☀️ Try build successful - checks-actions |
Queued c071c3594f1d95ba283af8252d803e1b74690fe0 with parent f24ce9b, future comparison URL. |
Finished benchmarking try commit (c071c3594f1d95ba283af8252d803e1b74690fe0): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
The performance improvements seem to have gone away. r=me, if you still want to land it |
@Aaron1011 any updates? |
Without any net performance improvement, landing this would probably just be unnecessary churn. |
This ensures that a codegen unit DepNode does not have a direct
dependency on the crate's attributes