Dan Gohman afc36a9520 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. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@70636 91177308-0d34-0410-b5e6-96231b3b80d8		2009-05-02 18:29:22 +00:00
..
AddrModeMatcher.h
BasicBlockUtils.h	Previously, RecursivelyDeleteDeadInstructions provided an option	2009-05-02 18:29:22 +00:00
BasicInliner.h
Cloning.h
FunctionUtils.h
InlineCost.h
Local.h	Previously, RecursivelyDeleteDeadInstructions provided an option	2009-05-02 18:29:22 +00:00
PromoteMemToReg.h
UnifyFunctionExitNodes.h
UnrollLoop.h
ValueMapper.h