Dan Gohman a79cce4aef Previously, RecursivelyDeleteDeadInstructions provided an option ... of returning a list of pointers to Values that are deleted. This was unsafe, because the pointers in the list are, by nature of what RecursivelyDeleteDeadInstructions does, always dangling. Replace this with a simple callback mechanism. This may eventually be removed if all clients can reasonably be expected to use CallbackVH. Use this to factor out the dead-phi-cycle-elimination code from LSR utility function, and generalize it to use the RecursivelyDeleteTriviallyDeadInstructions utility function. This makes LSR more aggressive about eliminating dead PHI cycles; adjust tests to either be less trivial or to simply expect fewer instructions. llvm-svn: 70636		2009-05-02 18:29:22 +00:00
..
Alpha
ARM	Previously, RecursivelyDeleteDeadInstructions provided an option	2009-05-02 18:29:22 +00:00
CBackend
CellSPU	Revert 67132. This is breaking some objective-c apps.	2009-03-25 20:20:11 +00:00
CPP	'The attached patch fixes an issue where llc -march=cpp fails with	2009-05-01 23:54:26 +00:00
Generic	Disable the load-shrinking optimization from looking at	2009-04-29 03:45:07 +00:00
IA64
Mips
PowerPC	Second attempt:	2009-04-29 00:15:41 +00:00
SPARC
X86	Previously, RecursivelyDeleteDeadInstructions provided an option	2009-05-02 18:29:22 +00:00
XCore	testcase for PR3898	2009-04-18 20:49:22 +00:00