llvm/test/CodeGen/X86/eh-label.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

25 lines
517 B
LLVM

; RUN: llc < %s -mtriple=x86_64-pc-linux | FileCheck %s
; Test that we don't crashe if the .Lfunc_end0 name is taken.
declare void @g()
define void @f() personality i8* bitcast (void ()* @g to i8*) {
bb0:
call void asm ".Lfunc_end0:", ""()
; CHECK: #APP
; CHECK-NEXT: .Lfunc_end0:
; CHECK-NEXT: #NO_APP
invoke void @g() to label %bb2 unwind label %bb1
bb1:
landingpad { i8*, i32 }
catch i8* null
call void @g()
ret void
bb2:
ret void
; CHECK: [[END:.Lfunc_end.*]]:
; CHECK: .long [[END]]-
}