maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/Transforms/CodeExtractor/2004-11-12-InvokeExtract.ll

19 lines
513 B
LLVM
Raw Normal View History

Change tests from "opt %s" to "opt < %s" so that opt doesn't see the input filename so that opt doesn't print the input filename in the output so that grep lines in the tests don't unintentionally match strings in the input filename. llvm-svn: 81537
2009-09-12 02:01:28 +08:00
; RUN: opt < %s -extract-blocks -disable-output
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 llvm-svn: 239940
2015-06-18 04:52:32 +08:00
define i32 @foo() personality i32 (...)* @__gcc_personality_v0 {
Remove llvm-upgrade and update test cases. llvm-svn: 47793
2008-03-01 17:15:35 +08:00
br label %EB
EB: ; preds = %0
%V = invoke i32 @foo( )
to label %Cont unwind label %Unw ; <i32> [#uses=1]
Cont: ; preds = %EB
ret i32 %V
Unw: ; preds = %EB
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 llvm-svn: 239940
2015-06-18 04:52:32 +08:00
%exn = landingpad { i8*, i32 }
Update to new EH model. llvm-svn: 140177
2011-09-21 04:21:16 +08:00
catch i8* null
resume { i8*, i32 } %exn
New testcase llvm-svn: 17698
2004-11-13 08:06:32 +08:00
}
Remove llvm-upgrade and update test cases. llvm-svn: 47793
2008-03-01 17:15:35 +08:00
Update to new EH model. llvm-svn: 140177
2011-09-21 04:21:16 +08:00
declare i32 @__gcc_personality_v0(...)