llvm-6502/test/Transforms/SCCP/2009-01-14-IPSCCP-Invoke.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

27 lines
559 B
LLVM

; RUN: opt < %s -ipsccp -S | grep "ret i32 42"
; RUN: opt < %s -ipsccp -S | grep "ret i32 undef"
; PR3325
define i32 @main() personality i8* bitcast (i32 (...)* @__gxx_personality_v0 to i8*) {
%tmp1 = invoke i32 @f()
to label %UnifiedReturnBlock unwind label %lpad
lpad:
%val = landingpad { i8*, i32 }
cleanup
unreachable
UnifiedReturnBlock:
ret i32 %tmp1
}
define internal i32 @f() {
ret i32 42
}
declare i8* @__cxa_begin_catch(i8*) nounwind
declare void @__cxa_end_catch()
declare i32 @__gxx_personality_v0(...)