llvm/test/Transforms/Inline/2003-09-14-InlineValue.ll
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

26 lines
631 B
LLVM

; RUN: opt < %s -inline -disable-output
declare i32 @External()
define internal i32 @Callee() {
%I = call i32 @External( ) ; <i32> [#uses=2]
%J = add i32 %I, %I ; <i32> [#uses=1]
ret i32 %J
}
define i32 @Caller() personality i32 (...)* @__gxx_personality_v0 {
%V = invoke i32 @Callee( )
to label %Ok unwind label %Bad ; <i32> [#uses=1]
Ok: ; preds = %0
ret i32 %V
Bad: ; preds = %0
%exn = landingpad {i8*, i32}
cleanup
ret i32 0
}
declare i32 @__gxx_personality_v0(...)