forked from OSchip/llvm-project
75a001ba78
JumpThreading claims to preserve LVI, but it doesn't preserve the analyses which LVI holds a reference to (e.g. the Dominator). In the current pass manager infrastructure, after JT runs, the PM frees these analyses (including DominatorTree) but preserves LVI. CorrelatedValuePropagation runs immediately after and queries a corrupted domtree, causing weird miscompiles. This commit disables the preservation of LVI for the time being. Eventually, we should either move LVI to a proper dependency tracking mechanism (i.e. an analyses shouldn't hold references to other analyses and compute them on demand if needed), or we should teach all the passes preserving LVI to preserve the analyses LVI depends on. The new pass manager has a mechanism to invalidate LVI in case one of the analyses it depends on becomes invalid, so this problem shouldn't exist (at least not in this immediate form), but handling of analyses holding references is still a very delicate subject. Fixes PR33917 (and rustc). llvm-svn: 309355 |
||
|---|---|---|
| .. | ||
| 2008-11-27-EntryMunge.ll | ||
| 2010-08-26-and.ll | ||
| 2011-04-02-SimplifyDeadBlock.ll | ||
| 2011-04-14-InfLoop.ll | ||
| 2012-07-19-NoSuccessorIndirectBr.ll | ||
| and-and-cond.ll | ||
| and-cond.ll | ||
| assume-edge-dom.ll | ||
| assume.ll | ||
| basic.ll | ||
| branch-no-const.ll | ||
| compare.ll | ||
| conservative-lvi.ll | ||
| crash.ll | ||
| degenerate-phi.ll | ||
| fold-not-thread.ll | ||
| guards.ll | ||
| implied-cond.ll | ||
| indirectbr.ll | ||
| induction.ll | ||
| landing-pad.ll | ||
| lvi-load.ll | ||
| no-irreducible-loops.ll | ||
| or-undef.ll | ||
| phi-eq.ll | ||
| phi-known.ll | ||
| pr9331.ll | ||
| pr15851_hang.ll | ||
| pr22086.ll | ||
| pr26096.ll | ||
| pr27840.ll | ||
| pr33605.ll | ||
| pr33917.ll | ||
| range-compare.ll | ||
| select.ll | ||
| static-profile.ll | ||
| thread-cmp.ll | ||
| thread-loads.ll | ||
| update-edge-weight.ll | ||