Chandler Carruth 908d4514f6 Fix a long-standing miscompile in the load analysis that was uncovered ... by my refactoring of this code. The method isSafeToLoadUnconditionally assumes that the load will proceed with the preferred type alignment. Given that, it has to ensure that the alloca or global is at least that aligned. It has always done this historically when a datalayout is present, but has never checked it when the datalayout is absent. When I refactored the code in r220156, I exposed this path when datalayout was present and that turned the latent bug into a patent bug. This fixes the issue by just removing the special case which allows folding things without datalayout. This isn't worth the complexity of trying to tease apart when it is or isn't safe without actually knowing the preferred alignment. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@220161 91177308-0d34-0410-b5e6-96231b3b80d8		2014-10-19 08:17:50 +00:00
..
2010-06-26-MultipleReturnValues.ll
accum_recursion.ll
ackermann.ll
basic.ll	Revert "TRE: make TRE a bit more aggressive"	2014-10-17 21:25:48 +00:00
dont_reorder_load.ll
dup_tail.ll
inf-recursion.ll
reorder_load.ll	Fix a long-standing miscompile in the load analysis that was uncovered	2014-10-19 08:17:50 +00:00
setjmp.ll