-
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
Fix perf issue for auto trait selection #95333
Conversation
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit ad88732 with merge 9db3bca9e8b8c644abfdd58ef3114d02f9f7e03b... |
☀️ Try build successful - checks-actions |
Queued 9db3bca9e8b8c644abfdd58ef3114d02f9f7e03b with parent bc881e8, future comparison URL. |
Let's run another perf check to see if there is any difference with one field removed. @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit bd51f17 with merge 00ed864234397653296be8e49cfa858c092ccd63... |
☀️ Try build successful - checks-actions |
Finished benchmarking commit (9db3bca9e8b8c644abfdd58ef3114d02f9f7e03b): comparison url. Summary: This benchmark run shows 22 relevant improvements 🎉 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. @bors rollup=never |
@bors r+ rollup=never |
📌 Commit bd51f17 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (3badf5c): comparison url. Summary: This benchmark run shows 20 relevant improvements 🎉 to instruction counts.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Follow-up of #95069 which fixes the perf issue introduced by it.
r? @oli-obk