-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
incr.comp.: Enable query result caching for many more queries #46556
Conversation
@bors r+ |
📌 Commit a16f296 has been approved by |
@bors p=1 -- incremental is high priority |
⌛ Testing commit a16f296a55d0af8a5a1f12b097ff8623d7a9f186 with merge 24ee46af90b6e79c43b7c3c9aa4ecfc1f01e025b... |
💔 Test failed - status-travis |
Legit.
|
These were already broken for debug builds.
…-Zincremental-verify-ich
a16f296
to
539e171
Compare
Rebased. @bors r=nmatsakis |
📌 Commit 539e171 has been approved by |
…akis incr.comp.: Enable query result caching for many more queries Newly cached queries are: * const_is_rvalue_promotable_to_static * trans_fulfill_obligation * optimized_mir * unsafety_check_result * borrowck * mir_borrowck * mir_const_qualif * contains_extern_indicator * def_symbol_name * symbol_name This also includes the stricter `Span` hashing first mentioned in #46490, which will lead to more false positives in release builds but overall is more correct -- and necessary for caching MIR. Hopefully we will soon be able to reduce the rate of false positives again by factoring `Span` out of MIR. r? @nikomatsakis
☀️ Test successful - status-appveyor, status-travis |
Newly cached queries are:
This also includes the stricter
Span
hashing first mentioned in #46490, which will lead to more false positives in release builds but overall is more correct -- and necessary for caching MIR. Hopefully we will soon be able to reduce the rate of false positives again by factoringSpan
out of MIR.r? @nikomatsakis