-
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
Turn vtable_allocation() into a query #89619
Conversation
Some changes occured to rustc_codegen_cranelift cc @bjorn3 Some changes occured to the CTFE / Miri engine cc @rust-lang/miri |
r? @davidtwco (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 59a9346bfc4080a60062dd3be0faefef8ec1181e with merge d366508c69d893916d86d7dd00ab980cccf50812... |
☀️ Try build successful - checks-actions |
Queued d366508c69d893916d86d7dd00ab980cccf50812 with parent ca8078d, future comparison URL. |
Finished benchmarking commit (d366508c69d893916d86d7dd00ab980cccf50812): comparison url. Summary: This change led to small 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 |
I just realized that the test case does not actually do what I expected it to do. It does work -- but only by accident. I'll rewrite it to be more robust. |
Implementation LGTM; r=me once the test is adjusted as necessary. |
59a9346
to
970bdf7
Compare
I updated the test case with an explanation of what's actually happening. |
This comment has been minimized.
This comment has been minimized.
970bdf7
to
b7cc991
Compare
@bors r=nagisa |
📌 Commit b7cc991 has been approved by |
@bors p=1 (since the PR is beta-accepted) |
☀️ Test successful - checks-actions |
Finished benchmarking commit (44995f7): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
[beta] backports - 2229: Consume IfLet expr rust-lang#89282 - Wrapper for -Z gcc-ld=lld to invoke rust-lld with the correct flavor rust-lang#89288 - Fix unsound optimization with explicit variant discriminants rust-lang#89489 - Fix stabilization version for bindings_after_at rust-lang#89605 - Turn vtable_allocation() into a query rust-lang#89619 - Revert "Stabilize Iterator::intersperse()" rust-lang#89638 - Ignore type of projections for upvar capturing rust-lang#89648 - ~~Add Poll::ready and~~ revert stabilization of task::ready! rust-lang#89651 - CI: Use mirror for libisl downloads for more docker dist builds rust-lang#89661 - Use correct edition for panic in [debug_]assert!(). rust-lang#89622 - Switch to our own mirror of libisl plus ct-ng oldconfig fixes rust-lang#89599 - Emit item no type error even if type inference fails rust-lang#89585 - Revert enum discriminants rust-lang#89884
Turn vtable_allocation() into a query This PR removes the untracked vtable-const-allocation cache from the `tcx` and turns the `vtable_allocation()` method into a query. The change is pretty straightforward and should be backportable without too much effort. Fixes rust-lang#89598.
This PR removes the untracked vtable-const-allocation cache from the
tcx
and turns thevtable_allocation()
method into a query.The change is pretty straightforward and should be backportable without too much effort.
Fixes #89598.