Tim Northover 0e34491fef GVN: tolerate an instruction being replaced without existing in the leaderboard ... Sometimes an incidentally created instruction can duplicate a Value used elsewhere. It then often doesn't end up in the leader table. If it's later removed, we attempt to remove it from the leader table and segfault. Instead we should just ignore the removal request, which won't cause any problems. The reverse situation, where the original instruction is replaced by the new one (which you might think could leave the leader table empty) cannot occur, because the incidental instruction will never be found in the first place. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@242199 91177308-0d34-0410-b5e6-96231b3b80d8		2015-07-14 21:03:18 +00:00
..
Hello	Revert r240137 (Fixed/added namespace ending comments using clang-tidy. NFC)	2015-06-23 09:49:53 +00:00
InstCombine	[InstSimplify] Teach InstSimplify how to simplify extractelement	2015-07-13 01:15:53 +00:00
Instrumentation	Revert the new EH instructions	2015-07-10 07:15:17 +00:00
IPO	Remove unused variable.	2015-07-13 14:43:33 +00:00
ObjCARC	Revert r240137 (Fixed/added namespace ending comments using clang-tidy. NFC)	2015-06-23 09:49:53 +00:00
Scalar	GVN: tolerate an instruction being replaced without existing in the leaderboard	2015-07-14 21:03:18 +00:00
Utils	Update enforceKnownAlignment after the isWeakForLinker semantic change	2015-07-14 00:11:08 +00:00
Vectorize	Avoid using Loop::getSubLoopsVector.	2015-07-13 17:21:14 +00:00
CMakeLists.txt
LLVMBuild.txt
Makefile