Sanjay Patel 14384c2977 [Analysis][LoopVectorize] rename "Unsafe" variables/methods; NFC ... Similar to b3a33553aec7, but this shows a TODO and a potential miscompile is already present. We are tracking an FP instruction that does *not* have FMF (reassoc) properties, so calling that "Unsafe" seems opposite of the common reading. I also removed one getter method by rolling the null check into the access. Further simplification may be possible. The motivation is to clean up the interactions between FMF and function-level attributes in these classes and their callers. The new test shows that there is an existing bug somewhere in the callers. We assumed that the original code was fully 'fast' and so we produced IR with 'fast' even though it was just 'reassoc'.		2021-03-04 10:40:26 -05:00
..
Inputs/ir2native_x86_64_model
AliasAnalysisTest.cpp	[AA] Cache (optionally) estimated PartialAlias offsets.	2021-03-02 19:04:15 +03:00
AliasSetTrackerTest.cpp
AssumeBundleQueriesTest.cpp
BasicAliasAnalysisTest.cpp
BlockFrequencyInfoTest.cpp
BranchProbabilityInfoTest.cpp
CallGraphTest.cpp
CaptureTrackingTest.cpp
CFGTest.cpp
CGSCCPassManagerTest.cpp
CMakeLists.txt
ConstraintSystemTest.cpp
DDGTest.cpp
DivergenceAnalysisTest.cpp
DomTreeUpdaterTest.cpp
FunctionPropertiesAnalysisTest.cpp
GlobalsModRefTest.cpp
IRSimilarityIdentifierTest.cpp
IVDescriptorsTest.cpp	[Analysis][LoopVectorize] rename "Unsafe" variables/methods; NFC	2021-03-04 10:40:26 -05:00
LazyCallGraphTest.cpp
LoadsTest.cpp
LoopInfoTest.cpp
LoopNestTest.cpp
MemoryBuiltinsTest.cpp
MemorySSATest.cpp
PhiValuesTest.cpp
ProfileSummaryInfoTest.cpp
ScalarEvolutionTest.cpp
SparsePropagation.cpp
TargetLibraryInfoTest.cpp
TBAATest.cpp
TFUtilsTest.cpp
UnrollAnalyzerTest.cpp
ValueLatticeTest.cpp
ValueTrackingTest.cpp
VectorFunctionABITest.cpp
VectorUtilsTest.cpp