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-02-01-ReturnAttrs.ll
2008-07-02-array-indexing.ll
2008-09-07-CGUpdate.ll
2008-09-08-CGUpdateSelfEdge.ll
aggregate-promote.ll
attrs.ll
basictest.ll
byval-2.ll
byval.ll
callgraph-update.ll
chained.ll
control-flow2.ll
control-flow.ll
crash.ll	Move the personality function from LandingPadInst to Function	2015-06-17 20:52:32 +00:00
dbg.ll	IR: Give 'DI' prefix to debug info metadata	2015-04-29 16:38:44 +00:00
fp80.ll
inalloca.ll
pr3085.ll
reserve-tbaa.ll
sret.ll	ArgumentPromotion: Drop sret attribute on functions that are only called directly.	2015-06-10 21:14:34 +00:00
tail.ll
variadic.ll	[opaque pointer type] Add textual IR support for explicit type parameter to the call instruction	2015-04-16 23:24:18 +00:00