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
..
2002-03-28-UninitializedVal.ll
2002-05-01-ShouldNotPromoteThisAlloca.ll
2003-04-10-DFNotFound.ll
2003-04-18-DeadBlockProblem.ll
2003-04-24-MultipleIdenticalSuccessors.ll
2003-06-26-IterativePromote.ll
2003-10-05-DeadPHIInsertion.ll
2005-06-30-ReadBeforeWrite.ll
2005-11-28-Crash.ll
2007-08-27-VolatileLoadsStores.ll
atomic.ll
ConvertDebugInfo2.ll	IR: Give 'DI' prefix to debug info metadata	2015-04-29 16:38:44 +00:00
ConvertDebugInfo.ll	IR: Give 'DI' prefix to debug info metadata	2015-04-29 16:38:44 +00:00
crash.ll	Move the personality function from LandingPadInst to Function	2015-06-17 20:52:32 +00:00
ignore-lifetime.ll
PromoteMemToRegister.ll
UndefValuesMerge.ll