maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/Other/2008-10-15-MissingSpace.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

17 lines
379 B
LLVM
Raw Normal View History

Using "not grep" is brittle as the test passes if llvm-as fails. Fix the testcase to be valid IL and uses FileCheck. Thanks to NAKAMURA Takumi for noticing it. llvm-svn: 168427
2012-11-21 22:17:23 +08:00
; RUN: llvm-as < %s | llvm-dis | FileCheck %s
Testcase for PR2894. llvm-svn: 57604
2008-10-16 06:34:34 +08:00
; PR2894
declare void @g()
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 void @f() personality i32 (...)* @__gxx_personality_v0 {
Using "not grep" is brittle as the test passes if llvm-as fails. Fix the testcase to be valid IL and uses FileCheck. Thanks to NAKAMURA Takumi for noticing it. llvm-svn: 168427
2012-11-21 22:17:23 +08:00
; CHECK: invoke void @g()
; CHECK: to label %d unwind label %c
invoke void @g() to label %d unwind label %c
d:
ret void
Update to new EH scheme. llvm-svn: 138906
2011-09-01 05:44:24 +08:00
c:
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 scheme. llvm-svn: 138906
2011-09-01 05:44:24 +08:00
cleanup
ret void
Testcase for PR2894. llvm-svn: 57604
2008-10-16 06:34:34 +08:00
}
Update to new EH scheme. llvm-svn: 138906
2011-09-01 05:44:24 +08:00
declare i32 @__gxx_personality_v0(...)