about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2021-09-21 13:25:14 +0000
committerbors <bors@rust-lang.org>2021-09-21 13:25:14 +0000
commit7743c9fadd64886d537966ba224b9c20e6014a59 (patch)
treeb31aebe2d0bf09a6bfffb657b43998e45f1b42a0 /compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp
parentdda2a0eca4a70acbdd2b65f5fc5e4cd38c39351b (diff)
parent6dbb9d4eee0a2789a74bb2d4b8228626f7cd741c (diff)
downloadrust-7743c9fadd64886d537966ba224b9c20e6014a59.tar.gz
rust-7743c9fadd64886d537966ba224b9c20e6014a59.zip
Auto merge of #89125 - Aaron1011:remove-intercrate-cache, r=jackh726
Don't use projection cache or candidate cache in intercrate mode

Fixes #88969

It appears that *just* disabling the evaluation cache (in #88994)
leads to other issues involving intercrate mode caching. I suspect
that since we now always end up performing the full evaluation
in intercrate mode, we end up 'polluting' the candidate and projection
caches with results that depend on being in intercrate mode in some way.
Previously, we might have hit a cached evaluation (stored during
non-intercrate mode), and skipped doing this extra work in
intercrate mode.

The whole situation with intercrate mode caching is turning into
a mess. Ideally, we would remove intercrate mode entirely - however,
this might require waiting on Chalk.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions