llvm-project/llvm/test/Assembler/2003-04-15-ConstantInitAsse...

; RUN: not llvm-as < %s >/dev/null 2> %t
; RUN: grep "struct initializer doesn't match struct element type" %t
; Test the case of a misformed constant initializer
; This should cause an assembler error, not an assertion failure!
@0 = constant { i32 } { float 1.0 }
Make tests which first provide a negative assertion via 'not', then a pipeline, and then a positive assertion via grep, use two RUN lines instead. Supporting these complex ideas of 'success' and 'failure' across multiple stages of a pipeline is brittle in the shell world, and would block switching to ShTest format; it only worked due to contrivances introduced by the TclTest format. Writing this as two separate RUN lines seems clearer in any event. This is another step toward completely removing TclTests from lit. llvm-svn: 159524 2012-07-02 20:23:19 +08:00			`; RUN: not llvm-as < %s >/dev/null 2> %t`
			`; RUN: grep "struct initializer doesn't match struct element type" %t`
New testcase that triggered assertion failure. llvm-svn: 5776 2003-04-16 00:07:05 +08:00			`; Test the case of a misformed constant initializer`
			`; This should cause an assembler error, not an assertion failure!`
Make "@name =" mandatory for globals in .ll files. An oddity of the .ll syntax is that the "@var = " in @var = global i32 42 is optional. Writing just global i32 42 is equivalent to @0 = global i32 42 This means that there is a pretty big First set at the top level. The current implementation maintains it manually. I was trying to refactor it, but then started wondering why keep it a all. I personally find the above syntax confusing. It looks like something is missing. This patch removes the feature and simplifies the parser. llvm-svn: 269096 2016-05-11 02:22:45 +08:00			`@0 = constant { i32 } { float 1.0 }`