-
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
Avoid unwrap_or_else
in RawVec::allocate_in
.
#73882
Avoid unwrap_or_else
in RawVec::allocate_in
.
#73882
Conversation
This reduces the amount of LLVM IR generated by up to 1 or 2%.
@bors try @rust-timer queue |
Awaiting bors try build completion |
@bors rollup=never |
⌛ Trying commit 3f79d2f with merge 1a70453c35125c6657c8e370c6f497f9ec9c41c9... |
☀️ Try build successful - checks-azure |
Queued 1a70453c35125c6657c8e370c6f497f9ec9c41c9 with parent a1528c4, future comparison URL. |
Finished benchmarking try commit (1a70453c35125c6657c8e370c6f497f9ec9c41c9): comparison url. |
@bors r+ |
📌 Commit 3f79d2f has been approved by |
The CI run shows small but clear benefits of up to 1% across numerous benchmarks. |
@bors p=1 |
⌛ Testing commit 3f79d2f with merge ea4a9c72845bbea7462e3fddff0e7a19c9ec6bb1... |
@bors r- |
@bors r=Amanieu retry yielding to rollup |
@bors r=Amanieu (@Manishearth I think "retry" retried the |
Or maybe bors is just borked? This still isn't in the queue. |
Maybe closing the PR while it was tested has broke bors? |
@bors r- |
@bors r=Amanieu |
📌 Commit 3f79d2f has been approved by |
yeah bors has been acting weird, the yield feature is broken too |
⌛ Testing commit 3f79d2f with merge 1462072fca19e34db73be4155857a097c17b92aa... |
@bors retry yield |
I'll be letting rollup=nevers filter through soon enough |
☀️ Test successful - checks-actions, checks-azure |
Perf results show a win, as expected. |
This reduces the amount of LLVM IR generated by up to 1 or 2%.
r? @Amanieu