David Majnemer cc714e2142 Move the personality function from LandingPadInst to Function ... The personality routine currently lives in the LandingPadInst. This isn't desirable because: - All LandingPadInsts in the same function must have the same personality routine. This means that each LandingPadInst beyond the first has an operand which produces no additional information. - There is ongoing work to introduce EH IR constructs other than LandingPadInst. Moving the personality routine off of any one particular Instruction and onto the parent function seems a lot better than have N different places a personality function can sneak onto an exceptional function. Differential Revision: http://reviews.llvm.org/D10429 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@239940 91177308-0d34-0410-b5e6-96231b3b80d8		2015-06-17 20:52:32 +00:00
..
CMakeLists.txt
InstCombineAddSub.cpp
InstCombineAndOrXor.cpp
InstCombineCalls.cpp	Reapply 239795 - [InstCombine] Propagate non-null facts to call parameters	2015-06-16 20:24:25 +00:00
InstCombineCasts.cpp
InstCombineCompares.cpp	[InstCombine][NFC] Add a `break;` statement.	2015-06-05 18:04:46 +00:00
InstCombineInternal.h
InstCombineLoadStoreAlloca.cpp
InstCombineMulDivRem.cpp
InstCombinePHI.cpp
InstCombineSelect.cpp	[InstCombine, InstSimplify] Move xforms from Combine to Simplify	2015-06-06 22:40:21 +00:00
InstCombineShifts.cpp
InstCombineSimplifyDemanded.cpp
InstCombineVectorOps.cpp
InstructionCombining.cpp	Move the personality function from LandingPadInst to Function	2015-06-17 20:52:32 +00:00
LLVMBuild.txt
Makefile