llvm-mirror/test/Transforms/SimplifyCFG/2007-11-22-InvokeNoUnwind.ll

; RUN: opt < %s -simplifycfg -S | FileCheck %s

; CHECK-NOT: invoke

declare i32 @func(i8*) nounwind

define i32 @test() personality i32 (...)* @__gxx_personality_v0 {
	invoke i32 @func( i8* null )
			to label %Cont unwind label %Other		; <i32>:1 [#uses=0]

Cont:		; preds = %0
	ret i32 0

Other:		; preds = %0
	landingpad { i8*, i32 }
		catch i8* null
	ret i32 1
}

declare i32 @__gxx_personality_v0(...)
Converted 8x tests of SimplifyCFG to use FileCheck instead of grep. llvm-svn: 179087 2013-04-09 07:18:53 +02:00			`; RUN: opt < %s -simplifycfg -S \| FileCheck %s`

			`; CHECK-NOT: invoke`
Turn invokes of nounwind functions into ordinary calls. llvm-svn: 44280 2007-11-22 23:24:59 +01:00
			`declare i32 @func(i8*) nounwind`

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-17 22:52:32 +02:00			`define i32 @test() personality i32 (...)* @__gxx_personality_v0 {`
Add some convenience methods for querying attributes, and use them. llvm-svn: 44403 2007-11-28 18:07:01 +01:00			`invoke i32 @func( i8* null )`
Turn invokes of nounwind functions into ordinary calls. llvm-svn: 44280 2007-11-22 23:24:59 +01:00			`to label %Cont unwind label %Other ; <i32>:1 [#uses=0]`

			`Cont: ; preds = %0`
			`ret i32 0`

			`Other: ; preds = %0`
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-17 22:52:32 +02:00			`landingpad { i8*, i32 }`
Don't promote asynch EH invokes of nounwind functions to calls If the landingpad of the invoke is using a personality function that catches asynch exceptions, then it can catch a trap. Also add some landingpads to invalid LLVM IR test cases that lack them. Over-the-shoulder reviewed by David Majnemer. llvm-svn: 228782 2015-02-11 02:23:16 +01:00			`catch i8* null`
Turn invokes of nounwind functions into ordinary calls. llvm-svn: 44280 2007-11-22 23:24:59 +01:00			`ret i32 1`
			`}`
Don't promote asynch EH invokes of nounwind functions to calls If the landingpad of the invoke is using a personality function that catches asynch exceptions, then it can catch a trap. Also add some landingpads to invalid LLVM IR test cases that lack them. Over-the-shoulder reviewed by David Majnemer. llvm-svn: 228782 2015-02-11 02:23:16 +01:00
			`declare i32 @__gxx_personality_v0(...)`