-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Restrict query recursion in needs_significant_drop
#93449
Restrict query recursion in needs_significant_drop
#93449
Conversation
r? @cjgillot (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 56ed8dc9e526e7a3a2546079781d417b220ad523 with merge 353c871303d82172f5490ff4d58c72a101481398... |
☀️ Try build successful - checks-actions |
Queued 353c871303d82172f5490ff4d58c72a101481398 with parent d08e816, future comparison URL. |
Finished benchmarking commit (353c871303d82172f5490ff4d58c72a101481398): comparison url. Summary: This benchmark run did not return any relevant results. 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. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf. @bors rollup=never |
Sorry @JakobDegen, I had forgotten about this PR. |
Overly aggressive use of the query system to improve caching lead to query cycles and consequently ICEs. This patch fixes this by restricting the use of the query system as a cache to those cases where it is definitely correct.
56ed8dc
to
5952d71
Compare
Rebased |
@bors r+ |
📌 Commit 5952d71 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (10cc7a6): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Overly aggressive use of the query system to improve caching lead to query cycles and consequently ICEs. This patch fixes this by restricting the use of the query system as a cache to those cases where it is definitely correct.
Closes #92725 .
This is essentially a revert of #90845 for the significant drop case only. The general
needs_drop
still does the same thing. The hope is that this is enough to preserve the performance improvements of that PR while fixing the ICE. Should get a perf run to verify that this is the case.cc @cjgillot