-
Notifications
You must be signed in to change notification settings - Fork 13.4k
MIR Body: Cache result of is_cyclic
call
#78454
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? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
Well since I've basically copied the predecessor cache, I've also copied it's testing strategy - i.e., none. I'll try to think about a way to avoid having to eagerly invalidate the caches. |
@bugadani - ping from triage - can you post your status on this PR? I've assigned it S-waiting-on-author because it looks like your PR still needs more work. |
@JohnCSimon I considered this PR "done", We could do a perf run to see if this change has any practical benefits, but otherwise I don't intend to make more modifications.
Do you have anything particular in mind? |
Switching back to S-waiting-on-review. |
@bors try @rust-timer queue |
Awaiting bors try build completion. |
⌛ Trying commit 039f54a4884803f65c1af5b6a8d7b9b5faba98bb with merge 7bf4a51615b645428dbc325d087b4e41d0ae0cca... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors try @rust-timer queue |
Awaiting bors try build completion. |
⌛ Trying commit 119879c with merge 08b66ce00bc45651e97c490b2aab2bd5dad9d9b1... |
☀️ Try build successful - checks-actions |
Queued 08b66ce00bc45651e97c490b2aab2bd5dad9d9b1 with parent 2ad5292, future comparison URL. @rustbot label: +S-waiting-on-perf |
Finished benchmarking try commit (08b66ce00bc45651e97c490b2aab2bd5dad9d9b1): 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 |
Up to -.8% instruction counts on many-assoc-items. No regressions :) |
@bors r+ Thanks! Once we get a third cache we should start thinking about a more generic concept for caches, but at this stage, copying seems absolutely right to me. |
📌 Commit 119879c has been approved by |
r? @oli-obk |
☀️ Test successful - checks-actions |
No description provided.