llvm/test/Transforms/Mem2Reg/crash.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

45 lines
696 B
LLVM

; RUN: opt < %s -mem2reg -S
; PR5023
declare i32 @test1f()
define i32 @test1() personality i32 (...)* @__gxx_personality_v0 {
entry:
%whichFlag = alloca i32
%A = invoke i32 @test1f()
to label %invcont2 unwind label %lpad86
invcont2:
store i32 %A, i32* %whichFlag
br label %bb15
bb15:
%B = load i32, i32* %whichFlag
ret i32 %B
lpad86:
%exn = landingpad {i8*, i32}
cleanup
br label %bb15
}
declare i32 @__gxx_personality_v0(...)
define i32 @test2() {
entry:
%whichFlag = alloca i32
br label %bb15
bb15:
%B = load i32, i32* %whichFlag
ret i32 %B
invcont2:
%C = load i32, i32* %whichFlag
store i32 %C, i32* %whichFlag
br label %bb15
}