llvm/test/Transforms/Inline/callgraph-update.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

37 lines
639 B
LLVM

; RUN: opt < %s -inline -loop-rotate -verify-dom-info -verify-loop-info -disable-output
; PR3601
declare void @solve()
define internal fastcc void @read() {
br label %bb4
bb3:
br label %bb4
bb4:
call void @solve()
br i1 false, label %bb5, label %bb3
bb5:
unreachable
}
define internal fastcc void @parse() {
call fastcc void @read()
ret void
}
define void @main() personality i32 (...)* @__gxx_personality_v0 {
invoke fastcc void @parse()
to label %invcont unwind label %lpad
invcont:
unreachable
lpad:
%exn = landingpad {i8*, i32}
cleanup
unreachable
}
declare i32 @__gxx_personality_v0(...)