-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Optimize unchecked indexing into chunks and chunks_mut #86823
Conversation
r? @kennytm (rust-highfive has picked a reviewer for you, use r? to override) |
Grepping through the compiler source doesn't show any uses of @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 24094a0 with merge 5c392fe307a7b9c6ca1d328ad7dbed69fb03897d... |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
Comparing CI build nightly with manually build stage1 can show unrelated results. |
I'd expect the compiler internals to be built differently, but shouldn't the output of the compiler remain comparable? |
☀️ Try build successful - checks-actions |
Queued 5c392fe307a7b9c6ca1d328ad7dbed69fb03897d with parent 2545459, future comparison URL. |
Finished benchmarking try commit (5c392fe307a7b9c6ca1d328ad7dbed69fb03897d): comparison url. Summary: This benchmark run did not return any significant 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. 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 |
@bors r+ |
📌 Commit 24094a0 has been approved by |
☀️ Test successful - checks-actions |
Awesome, thanks for working on this! |
Fixes #53340