forked from OSchip/llvm-project
8359511c62
During extraction, stale llvm.assume handles may be retained in the original function. The setup is: 1) CodeExtractor unregisters assumptions in the blocks that are to be extracted. 2) Extraction happens. There are now two functions: f1 and f1.extracted. 3) Leftover assumptions in f1 (/not/ removed as they were not in the set of blocks to be extracted) now have affected-value llvm.assume handles in f1.extracted. When assumptions for a value used in f1 are looked up, ValueTracking can assert as some of the handles are in the wrong function. To fix this, simply erase the llvm.assume calls in the extracted function. Alternatives include flushing the assumption cache in the original function, or walking all values used in the original function to prune stale affected-value handles. Both seem more expensive. Testing: check-llvm, LNT run with -mllvm -hot-cold-split enabled rdar://58460728 |
||
|---|---|---|
| .. | ||
| ASanStackFrameLayoutTest.cpp | ||
| BasicBlockUtilsTest.cpp | ||
| CMakeLists.txt | ||
| CloningTest.cpp | ||
| CodeExtractorTest.cpp | ||
| CodeMoverUtilsTest.cpp | ||
| FunctionComparatorTest.cpp | ||
| IntegerDivisionTest.cpp | ||
| LocalTest.cpp | ||
| LoopRotationUtilsTest.cpp | ||
| LoopUtilsTest.cpp | ||
| SSAUpdaterBulkTest.cpp | ||
| SizeOptsTest.cpp | ||
| UnrollLoopTest.cpp | ||
| VFABIUtils.cpp | ||
| ValueMapperTest.cpp | ||