llvm-mirror/test/Assembler/invalid-landingpad.ll

; RUN: not llvm-as < %s 2>&1 | FileCheck %s

; CHECK: clause argument must be a constant

define void @test(i32 %in) personality void()* null {
  landingpad {} filter i32 %in
}
Fix a bug in the LLParser where we failed to diagnose landingpads with non-constant clause operands. Fixing this also exposed a related issue where the landingpad under construction was not cleaned up when an error was raised, which would cause bad reference errors before the error could actually be printed. llvm-svn: 231634 2015-03-09 08:13:42 +01:00			`; RUN: not llvm-as < %s 2>&1 \| FileCheck %s`

			`; CHECK: clause argument must be a constant`

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 void @test(i32 %in) personality void()* null {`
			`landingpad {} filter i32 %in`
Fix a bug in the LLParser where we failed to diagnose landingpads with non-constant clause operands. Fixing this also exposed a related issue where the landingpad under construction was not cleaned up when an error was raised, which would cause bad reference errors before the error could actually be printed. llvm-svn: 231634 2015-03-09 08:13:42 +01:00			`}`