-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Add codegen tests for additional cases where noop iterators get optimized away #95695
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
(rust-highfive has picked a reviewer for you, use r? to override) |
d0d1e58
to
29db04d
Compare
@bors r+ rollup=iffy |
📌 Commit 29db04dc46b23cc889e297c4edbf31cccad648f9 has been approved by |
⌛ Testing commit 29db04dc46b23cc889e297c4edbf31cccad648f9 with merge 58d3248d6a416dedf5832f7bb30e2d0f7a408e31... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
A case of "works on my machine" 😔 |
…ized away Optimization have improved over time and now LLVM manages to optimize more in-place-collect noop-iterators to O(1) functions. This updates the codegen test to match.
29db04d
to
6935896
Compare
@rustbot ready It was the debug asserts being enabled in CI, I shouldn't have removed the |
@bors r+ |
📌 Commit 6935896 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (7b5408d): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
Optimizations have improved over time and now LLVM manages to optimize more in-place-collect noop-iterators to O(1) functions. This updates the codegen test to match.
Many but not all cases reported in #79308 work now.