Chandler Carruth 2817fc1e53 Fix ValueTracking to conclude that debug intrinsics are safe to ... speculate. Without this, loop rotate (among many other places) would suddenly stop working in the presence of debug info. I found this looking at loop rotate, and have augmented its tests with a reduction out of a very hot loop in yacr2 where failing to do this rotation costs sometimes more than 10% in runtime performance, perturbing numerous downstream optimizations. This should have no impact on performance without debug info, but the change in performance when debug info is enabled can be extreme. As a consequence (and this how I got to this yak) any profiling of performance problems should be treated with deep suspicion -- they may have been wildly innacurate of debug info was enabled for profiling. =/ Just a heads up. llvm-svn: 154263		2012-04-07 19:22:18 +00:00
..
2009-01-25-SingleEntryPhi.ll
alloca.ll
basic.ll
crash.ll
dbgvalue.ll	Fix ValueTracking to conclude that debug intrinsics are safe to	2012-04-07 19:22:18 +00:00
indirectbr.ll
lit.local.cfg	Replace all instances of dg.exp file with lit.local.cfg, since all tests are run with LIT now and now Dejagnu. dg.exp is no longer needed.	2012-02-16 06:28:33 +00:00
phi-duplicate.ll
PhiRename-1.ll
PhiSelfRefernce-1.ll
pr2639.ll
preserve-scev.ll
simplifylatch.ll