llvm/test/Feature/callingconventions.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

63 lines
1.1 KiB
LLVM

; RUN: llvm-as < %s | llvm-dis > %t1.ll
; RUN: llvm-as %t1.ll -o - | llvm-dis > %t2.ll
; RUN: diff %t1.ll %t2.ll
define fastcc void @foo() {
ret void
}
define coldcc void @bar() {
call fastcc void @foo( )
ret void
}
define void @structret({ i8 }* sret %P) {
call void @structret( { i8 }* sret %P )
ret void
}
define void @foo2() {
ret void
}
define coldcc void @bar2() {
call fastcc void @foo( )
ret void
}
define cc42 void @bar3() personality i32 (...)* @__gxx_personality_v0 {
invoke fastcc void @foo( )
to label %Ok unwind label %U
Ok:
ret void
U:
%exn = landingpad {i8*, i32}
cleanup
resume { i8*, i32 } %exn
}
define void @bar4() personality i32 (...)* @__gxx_personality_v0 {
call cc42 void @bar( )
invoke cc42 void @bar3( )
to label %Ok unwind label %U
Ok:
ret void
U:
%exn = landingpad {i8*, i32}
cleanup
resume { i8*, i32 } %exn
}
declare ghccc void @ghc_callee()
define void @ghc_caller() {
call ghccc void @ghc_callee()
ret void
}
declare i32 @__gxx_personality_v0(...)