llvm/test/Transforms/InstCombine/2004-01-13-InstCombineInvokePHI.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

32 lines
1.1 KiB
LLVM

; Test for a problem afflicting several C++ programs in the testsuite. The
; instcombine pass is trying to get rid of the cast in the invoke instruction,
; inserting a cast of the return value after the PHI instruction, but which is
; used by the PHI instruction. This is bad: because of the semantics of the
; invoke instruction, we really cannot perform this transformation at all at
; least without splitting the critical edge.
;
; RUN: opt < %s -instcombine -disable-output
declare i8* @test()
define i32 @foo() personality i32 (...)* @__gxx_personality_v0 {
entry:
br i1 true, label %cont, label %call
call: ; preds = %entry
%P = invoke i32* bitcast (i8* ()* @test to i32* ()*)( )
to label %cont unwind label %N ; <i32*> [#uses=1]
cont: ; preds = %call, %entry
%P2 = phi i32* [ %P, %call ], [ null, %entry ] ; <i32*> [#uses=1]
%V = load i32, i32* %P2 ; <i32> [#uses=1]
ret i32 %V
N: ; preds = %call
%exn = landingpad {i8*, i32}
cleanup
ret i32 0
}
declare i32 @__gxx_personality_v0(...)