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 |
||
|---|---|---|
| .. | ||
| 2002-01-31-UseStuckAround.ll | ||
| 2002-05-22-PHITest.ll | ||
| 2002-05-23-ZeroArgPHITest.ll | ||
| 2002-05-28-Crash-distilled.ll | ||
| 2002-05-28-Crash.ll | ||
| 2002-07-17-AssertionFailure.ll | ||
| 2002-07-17-PHIAssertion.ll | ||
| 2002-07-29-Segfault.ll | ||
| 2003-01-22-PredecessorProblem.ll | ||
| 2003-04-25-PHIPostDominateProblem.ll | ||
| 2003-06-11-InvalidCFG.ll | ||
| 2003-06-24-BadSuccessor.ll | ||
| 2003-06-24-BasicFunctionality.ll | ||
| 2003-09-10-UnwindInstFail.ll | ||
| 2003-09-15-InfLoopCrash.ll | ||
| 2003-11-16-MissingPostDominanceInfo.ll | ||
| 2004-05-04-UnreachableBlock.ll | ||
| 2005-02-17-PHI-Invoke-Crash.ll | ||
| basictest.ll | ||
| basictest1.ll | ||
| basictest2.ll | ||
| dce_pure_call.ll | ||
| dce_pure_invoke.ll | ||
| unreachable-function.ll | ||