-
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
Erase regions within vtable_trait_first_method_offset
#90536
Conversation
This comment has been minimized.
This comment has been minimized.
a4b6e85
to
d03283b
Compare
d03283b
to
8841204
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 8841204 with merge f155cf50ec3c87dad1e65b3a9a1a9203b159f7bc... |
☀️ Try build successful - checks-actions |
Queued f155cf50ec3c87dad1e65b3a9a1a9203b159f7bc with parent 473eaa4, future comparison URL. |
Finished benchmarking commit (f155cf50ec3c87dad1e65b3a9a1a9203b159f7bc): 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. 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. @bors rollup=never |
@bors r+ |
📌 Commit 8841204 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (2cff30b): 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 |
Fixes #90177 .
r? @jackh726