Adding RUN lines.

llvm-svn: 17528

llvm/test/Regression/Assembler/2002-01-24-BadSymbolTableAssert.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; This testcase failed due to a bad assertion in SymbolTable.cpp, removed in the 1.20 revision
 ; Basically the symbol table assumed that if there was an abstract type in the symbol table,
 ; [in this case for the entry %foo of type void(opaque)* ], that there should have also been

llvm/test/Regression/Assembler/2002-01-24-ValueRefineAbsType.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; This testcase used to fail due to a lack of this diff in Value.cpp:
 ; diff -r1.16 Value.cpp
 ; 11c11

llvm/test/Regression/Assembler/2002-02-19-TypeParsing.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
   %Hosp = type { int, int, int, { \2 *, { int, int, int, { [4 x \3], \2, \5, \6,
    int, int } * } *, \2 * }, { \2 *, { int, int, int, { [4 x \3], \2, \5, \6, int,
     int } * } *, \2 * }, { \2 *, { int, int, int, { [4 x \3], \2, \5, \6, int, int 

llvm/test/Regression/Assembler/2002-03-08-NameCollision.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; Method arguments were being checked for collisions at the global scope before
 ; the method object was created by the parser.  Because of this, false collisions
 ; could occur that would cause the following error message to be produced:

llvm/test/Regression/Assembler/2002-03-08-NameCollision2.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; Another name collision problem.  Here the problem was that if a forward 
 ; declaration for a method was found, that this would cause spurious conflicts
 ; to be detected between locals and globals.

llvm/test/Regression/Assembler/2002-04-04-PureVirtMethCall.ll

@@ -1,5 +1,7 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
   type { { \2 *, \4 ** },
          { \2 *, \4 ** }
        }
 
-implementation
+implementation

llvm/test/Regression/Assembler/2002-04-04-PureVirtMethCall2.ll

@@ -1,5 +1,7 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 %t = type { { \2*, \2 },
             { \2*, \2 }
           }
 
-implementation
+implementation

llvm/test/Regression/Assembler/2002-04-05-TypeParsing.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
   %Hosp = type {
                  { \2 *, { \2, \4 } * },
                  { \2 *, { \2, \4 } * }

llvm/test/Regression/Assembler/2002-05-02-InvalidForwardRef.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; It looks like the assembler is not forward resolving the function declaraion
 ; correctly.
 

llvm/test/Regression/Assembler/2002-05-02-ParseError.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; This should parse correctly without an 'implementation', but our current YACC
 ; based parser doesn't have the required 2 token lookahead...
 ; XFAIL: * 

llvm/test/Regression/Assembler/2002-08-15-CastAmbiguity.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 
 
 

llvm/test/Regression/Assembler/2002-08-15-ConstantExprProblem.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 %.LC0 = internal global [12 x sbyte] c"hello world\00"
 
 implementation   ; Functions:

llvm/test/Regression/Assembler/2002-08-15-UnresolvedGlobalReference.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 %.LC0 = internal global [12 x sbyte] c"hello world\00"          ; <[12 x sbyte]*> [#uses=1]
 
 implementation   ; Functions:

llvm/test/Regression/Assembler/2002-08-22-DominanceProblem.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; Dominance relationships is not calculated correctly for unreachable blocks,
 ; which causes the verifier to barf on this input.
 

llvm/test/Regression/Assembler/2002-10-08-LargeArrayPerformance.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; This testcase comes from the following really simple c file:
 ;
 ; int foo[30000];

llvm/test/Regression/Assembler/2002-10-15-NameClash.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 declare int "ArrayRef"([100 x int] * %Array)
 
 int "ArrayRef"([100 x int] * %Array) {

llvm/test/Regression/Assembler/2002-12-15-GlobalResolve.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 
 
 %X = external global %T* 

llvm/test/Regression/Assembler/2003-01-30-UnsignedString.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 
 %spell_order = global [4 x ubyte] c"\FF\00\F7\00"
 

llvm/test/Regression/Assembler/2003-02-02-ConstGlobal.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 
 %X = external global int
 %X = constant int 7

llvm/test/Regression/Assembler/2003-04-25-UnresolvedGlobalReference.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; There should be absolutely no problem with this testcase.
 
 implementation

llvm/test/Regression/Assembler/2003-05-15-SwitchBug.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 
 
 void %test(int %X) {

llvm/test/Regression/Assembler/2003-05-21-ConstantShiftExpr.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; Test that shift instructions can be used in constant expressions.
 
 global int shl (int 7, ubyte 19)

llvm/test/Regression/Assembler/2003-05-21-EmptyStructTest.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; The old C front-end never generated empty structures, now the new one
 ; can.  For some reason we never handled them in the parser. Wierd.
 

llvm/test/Regression/Assembler/2003-06-30-RecursiveTypeProblem.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 
 %MidFnTy = type void (void (%MidFnTy* )*)
 

llvm/test/Regression/Assembler/2003-10-04-NotMergingGlobalConstants.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 
 %T = type opaque
 %X = global %T* null

llvm/test/Regression/Assembler/2004-01-22-FloatNormalization.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; make sure that 'float' values have their value properly truncated.
 
 global float 0x1 

llvm/test/Regression/Assembler/2004-02-27-SelfUseAssertError.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 ; %inc2 uses it's own value, but that's ok, as it's unreachable!
 
 void %test() {

llvm/test/Regression/Assembler/2004-04-04-GetElementPtrIndexTypes.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 
 
 

llvm/test/Regression/Assembler/select.ll

@@ -1,3 +1,5 @@
+; RUN: llvm-as < %s -o /dev/null -f
+
 
 
 int %test(bool %C, int %V1, int %V2) {