Home
last modified time | relevance | path

Searched refs:ValueTracking (Results 1 – 11 of 11) sorted by relevance

/llvm-project-15.0.7/llvm/test/Transforms/LoopUnroll/
H A Dassume-timeout.ll4 ; This test caused a compile-time explosion in ValueTracking
/llvm-project-15.0.7/llvm/utils/gn/secondary/llvm/lib/Analysis/
H A DBUILD.gn131 "ValueTracking.cpp",
/llvm-project-15.0.7/llvm/lib/Analysis/
H A DCMakeLists.txt141 ValueTracking.cpp
/llvm-project-15.0.7/llvm/test/Transforms/InstCombine/
H A Dadd2.ll325 ; llvm.cttz, ValueTracking correctly intersects the range specified by the
329 ; ValueTracking uses that range.
351 ; intrinsic is more strict. Therefore, ValueTracking uses that range.
H A Dsimplify-libcalls.ll261 ; PR50885 - this would crash in ValueTracking.
H A Dand.ll606 ; FIXME: This test should only need -instsimplify (ValueTracking / computeKnownBits), not -passes=i…
/llvm-project-15.0.7/llvm/unittests/Analysis/
H A DValueTrackingTest.cpp614 TEST(ValueTracking, GuaranteedToTransferExecutionToSuccessor) { in TEST() argument
808 TEST(ValueTracking, propagatesPoison) { in TEST() argument
1069 TEST(ValueTracking, canCreatePoisonOrUndef) { in TEST() argument
/llvm-project-15.0.7/llvm/test/CodeGen/X86/
H A Dvec_minmax_match.ll4 ; These are actually tests of ValueTracking, and so may have test coverage in InstCombine or other
5 ; IR opt passes, but ValueTracking also affects the backend via SelectionDAGBuilder::visitSelect().
/llvm-project-15.0.7/llvm/test/Transforms/EarlyCSE/
H A Dcommute.ll777 ; a ValueTracking select pattern that required 'nsw'
798 ; a ValueTracking select pattern that required 'nsw'
/llvm-project-15.0.7/llvm/docs/
H A DStatepoints.rst126 well isolated to isSafeToSpeculate in ValueTracking.cpp.
H A DLangRef.rst16049 constant folding, instruction combining, KnownBits, and ValueTracking should