-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Small perf changes for InstCombine #79084
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
Conversation
r? @estebank (rust_highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion |
⌛ Trying commit 3d5a1e3 with merge d91a689b00fbcb98ad332dfba5c82a4f606d5695... |
☀️ Try build successful - checks-actions |
Queued d91a689b00fbcb98ad332dfba5c82a4f606d5695 with parent f5230fb, future comparison URL. |
Finished benchmarking try commit (d91a689b00fbcb98ad332dfba5c82a4f606d5695): 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 |
Seems like a small win for some benchmarks without any regressions. |
I think Oli might be a better reviewer for this? r? @oli-obk |
@bors r+ |
📌 Commit 0010fc8 has been approved by |
☀️ Test successful - checks-actions |
No description provided.