David Majnemer 5a57dbef33 IndVarSimplify: check if loop invariant expansion can trap ... IndVarSimplify is willing to move divide instructions outside of their loop bodies if they are invariant of the loop. However, it may not be safe to expand them if we do not know if they can trap. Instead, check to see if it is not safe to expand the instruction and skip the expansion. This fixes PR16041. Testcase by Rafael Ávila de Espíndola. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@183239 91177308-0d34-0410-b5e6-96231b3b80d8		2013-06-04 17:51:58 +00:00
..
Hello
InstCombine	Delete dead safety check.	2013-06-03 23:15:20 +00:00
Instrumentation	[asan] ASan Linux MIPS32 support (llvm part), patch by Jyun-Yan Y	2013-06-03 14:46:56 +00:00
IPO	Move getRealLinkageName to a common place and remove all the duplicates of it.	2013-06-01 17:51:14 +00:00
ObjCARC	[objc-arc] KnownSafe does not imply that it is safe to perform code motion across CFG edges since even if it is safe to remove RR pairs, we may still be able to move a retain/release into a loop.	2013-05-24 20:44:05 +00:00
Scalar	IndVarSimplify: check if loop invariant expansion can trap	2013-06-04 17:51:58 +00:00
Utils	Second part of pr16069	2013-06-04 14:11:59 +00:00
Vectorize	LoopVectorize: Change API call to get the backedge taken count	2013-05-31 21:48:56 +00:00
CMakeLists.txt
LLVMBuild.txt
Makefile