llvm/test/Transforms/Inline/2003-09-22-PHINodesInExceptionDest.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

33 lines
740 B
LLVM

; RUN: opt < %s -inline -disable-output
define i32 @main() personality i32 (...)* @__gxx_personality_v0 {
entry:
invoke void @__main( )
to label %Call2Invoke unwind label %LongJmpBlkPre
Call2Invoke: ; preds = %entry
br label %exit
LongJmpBlkPre: ; preds = %Call2Invoke, %entry
%i.3 = phi i32 [ 0, %entry ]
%exn = landingpad {i8*, i32}
cleanup
br label %exit
exit:
ret i32 0
}
define void @__main() {
call void @__llvm_getGlobalCtors( )
call void @__llvm_getGlobalDtors( )
ret void
}
declare i32 @__gxx_personality_v0(...)
declare void @__llvm_getGlobalCtors()
declare void @__llvm_getGlobalDtors()