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
..
2008-06-09-WeakProp.ll
2009-09-24-byval-ptr.ll	[opaque pointer type] Add textual IR support for explicit type parameter to gep operator	2015-03-13 18:20:45 +00:00
dangling-block-address.ll	[opaque pointer type] Add textual IR support for explicit type parameter to load instruction	2015-02-27 21:17:42 +00:00
deadarg.ll
global.ll	[opaque pointer type] Add textual IR support for explicit type parameter to load instruction	2015-02-27 21:17:42 +00:00
recursion.ll
return-argument.ll	Move the personality function from LandingPadInst to Function	2015-06-17 20:52:32 +00:00
return-constant.ll	Move the personality function from LandingPadInst to Function	2015-06-17 20:52:32 +00:00
return-constants.ll
user-with-multiple-uses.ll