llvm/test/Verifier/dominates.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

58 lines
1.3 KiB
LLVM

; RUN: not llvm-as < %s -o /dev/null 2>&1 | FileCheck %s
define i32 @f1(i32 %x) {
%y = add i32 %z, 1
%z = add i32 %x, 1
ret i32 %y
; CHECK: Instruction does not dominate all uses!
; CHECK-NEXT: %z = add i32 %x, 1
; CHECK-NEXT: %y = add i32 %z, 1
}
declare i32 @g()
define void @f2(i32 %x) personality i32 ()* @g {
bb0:
%y1 = invoke i32 @g() to label %bb1 unwind label %bb2
bb1:
ret void
bb2:
%y2 = phi i32 [%y1, %bb0]
%y3 = landingpad i32
cleanup
ret void
; CHECK: Instruction does not dominate all uses!
; CHECK-NEXT: %y1 = invoke i32 @g()
; CHECK-NEXT: to label %bb1 unwind label %bb2
; CHECK-NEXT: %y2 = phi i32 [ %y1, %bb0 ]
}
define void @f3(i32 %x) personality i32 ()* @g {
bb0:
%y1 = invoke i32 @g() to label %bb1 unwind label %bb2
bb1:
ret void
bb2:
%y2 = landingpad i32
cleanup
br label %bb3
bb3:
%y3 = phi i32 [%y1, %bb2]
ret void
; CHECK: Instruction does not dominate all uses!
; CHECK-NEXT: %y1 = invoke i32 @g()
; CHECK-NEXT: to label %bb1 unwind label %bb2
; CHECK-NEXT: %y3 = phi i32 [ %y1, %bb2 ]
}
define void @f4(i32 %x) {
bb0:
br label %bb1
bb1:
%y3 = phi i32 [%y1, %bb0]
%y1 = add i32 %x, 1
ret void
; CHECK: Instruction does not dominate all uses!
; CHECK-NEXT: %y1 = add i32 %x, 1
; CHECK-NEXT: %y3 = phi i32 [ %y1, %bb0 ]
}