David Majnemer c8b1f095a3 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 llvm-svn: 239940		2015-06-17 20:52:32 +00:00
..
2006-10-02-BreakCritEdges.ll	FileCheck-ize tests.	2012-04-24 10:45:44 +00:00
2007-01-14-BreakCritEdges.ll	Change tests from "opt %s" to "opt < %s" so that opt doesn't see the	2009-09-11 18:01:28 +00:00
2007-07-11-SplitBlock.ll	Eliminate more redundant llvm-as calls.	2009-09-11 18:17:12 +00:00
2007-07-12-SplitBlock.ll	Eliminate more redundant llvm-as calls.	2009-09-11 18:17:12 +00:00
basic.ll	[PM] Port domtree to the new pass manager (at last).	2015-01-14 10:19:28 +00:00
invoke.ll	Move the personality function from LandingPadInst to Function	2015-06-17 20:52:32 +00:00