Use llvm-upgrade these tests as they all use old assembly.

llvm-svn: 32130

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

@@ -1,10 +1,10 @@
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -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
-; named types by now.  This was obviously not the case here, and this is valid.  Assertion
-; disabled.
+; 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 named types by now.  This 
+; was obviously not the case here, and this is valid.  Assertion disabled.
 
 declare void "foo"(%bb)
 %bb = type int 

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

@@ -1,4 +1,4 @@
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -o /dev/null -f
 
 ; This testcase used to fail due to a lack of this diff in Value.cpp:
 ; diff -r1.16 Value.cpp
@@ -13,8 +13,8 @@
 ; >   if (OldTy == NewTy && !OldTy->isAbstract())
 ; >     Ty.removeUserFromConcrete();
 ;
-; This was causing an assertion failure, due to the "foo" Method object never releasing
-; it's reference to the opaque %bb value.
+; This was causing an assertion failure, due to the "foo" Method object never 
+; releasing it's reference to the opaque %bb value.
 ;
 declare void "foo"(%bb)
 

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

@@ -1,4 +1,4 @@
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -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,

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

@@ -1,8 +1,9 @@
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -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:
+; 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:
 ;
 ;    Redefinition of value named 'X' in the 'int *' type plane!
 ;

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

@@ -1,4 +1,4 @@
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -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

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

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

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

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

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

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

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

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

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

@@ -1,10 +1,9 @@
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -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: * 
 
-	%T = type int *
+%T = type int *
 
 %T %test() {
 	ret %T null

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

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

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

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

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

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

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

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

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

@@ -1,4 +1,4 @@
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -o /dev/null -f
 
 ; This testcase comes from the following really simple c file:
 ;

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

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

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

@@ -1,12 +1,9 @@
-; RUN: llvm-as < %s -o /dev/null -f
-
-
+; RUN: llvm-upgrade < %s | llvm-as -o /dev/null -f
 
 %X = external global %T* 
 %X = external global int *
 
 %T = type int
 
-
 implementation
 

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

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

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

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

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

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

test/Regression/Assembler/2003-05-15-AssemblerProblem.llx

@@ -1,7 +1,7 @@
 ; This bug was caused by two CPR's existing for the same global variable, 
 ; colliding in the Module level CPR map.
 
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -o /dev/null -f
 
 void %test() {
         call void (...)* cast (void (short*, int)* %AddString to void (...)*)(short* null, int 0)

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

@@ -1,6 +1,6 @@
-; RUN: llvm-as < %s -o /dev/null -f
-
+; RUN: llvm-upgrade < %s | llvm-as -o /dev/null -f
 
+; Check minimal switch statement
 
 void %test(int %X) {
   switch int %X, label %dest []

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

@@ -1,4 +1,4 @@
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -o /dev/null -f
 
 ; Test that shift instructions can be used in constant expressions.
 

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

@@ -1,4 +1,4 @@
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -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. Weird.

test/Regression/Assembler/2003-05-21-MalformedShiftCrash.llx

@@ -1,4 +1,4 @@
 ; Found by inspection of the code
-; RUN: llvm-as < %s 2>&1 | grep "Shift constant expression"
+; RUN: llvm-upgrade < %s | llvm-as -o /dev/null -f 2>&1 | grep "Shift constant expression"
 
 global int shr (float 1.0, ubyte 2)

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

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

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

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

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

@@ -1,4 +1,4 @@
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -o /dev/null -f
 
 ; %inc2 uses it's own value, but that's ok, as it's unreachable!
 

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

@@ -1,7 +1,4 @@
-; RUN: llvm-as < %s -o /dev/null -f
-
-
-
+; RUN: llvm-upgrade < %s | llvm-as -o /dev/null -f
 
 int *%t1({ float, int }* %X) {
 	%W = getelementptr { float, int }* %X, int 20, uint 1

test/Regression/Assembler/2004-11-28-InvalidTypeCrash.ll

@@ -1,3 +1,3 @@
-; RUN: (llvm-as < %s) 2>&1 | grep 'Cannot create a'
+; RUN: (llvm-upgrade < %s | llvm-as -o /dev/null -f) 2>&1 | grep 'Cannot create a'
 ; Test for PR463.  This program is erroneous, but should not crash llvm-as.
 %.FOO  = internal global %struct.none zeroinitializer

test/Regression/Assembler/2004-12-06-ConstantFloatRange.ll

@@ -1,4 +1,4 @@
-; RUN: llvm-as %s -o /dev/null 2>&1 | grep "constant invalid for type"
+; RUN: llvm-upgrade %s | llvm-as -o /dev/null -f 2>&1 | grep "constant invalid for type"
 ; XFAIL: *
 
 ;; This is a testcase for PR409

test/Regression/Assembler/2005-01-31-CallingAggregateFunction.ll

@@ -1,4 +1,4 @@
-; RUN: llvm-as %s -o /dev/null 2>&1 | grep "LLVM functions cannot return aggregate types"
+; RUN: llvm-upgrade %s | llvm-as -o /dev/null -f 2>&1 | grep "LLVM functions cannot return aggregate types"
 
 void %test() {
 	call {} %foo()

test/Regression/Assembler/2005-12-21-ZeroInitVector.ll

@@ -1,4 +1,4 @@
-; RUN: llvm-as < %s > /dev/null
+; RUN: llvm-upgrade < %s | llvm-as > /dev/null
 
 < 4 x int> %foo() {
   ret <4 x int> zeroinitializer

test/Regression/Assembler/2006-09-28-CrashOnInvalid.ll

@@ -1,6 +1,6 @@
 ; Test for PR902.  This program is erroneous, but should not crash llvm-as.
 ; This tests that a simple error is caught and processed correctly.
-; RUN: (llvm-as < %s) 2>&1 | grep 'FP constant invalid for type'
+; RUN: llvm-upgrade < %s | llvm-as 2>&1 | grep 'FP constant invalid for type'
 void %test() {
   add int 1, 2.0
   ret void

test/Regression/Assembler/ConstantExprFold.llx

@@ -1,7 +1,8 @@
-; This test checks to make sure that constant exprs fold in some simple situations
+; This test checks to make sure that constant exprs fold in some simple 
+; situations
 
 ; RUN: llvm-upgrade < %s | llvm-as | llvm-dis | not grep '(' &&
-; RUN: llvm-as < %s
+; RUN: llvm-upgrade < %s | llvm-as
 
 %A = global long 0
 

test/Regression/Assembler/select.ll

@@ -1,4 +1,4 @@
-; RUN: llvm-as < %s -o /dev/null -f
+; RUN: llvm-upgrade < %s | llvm-as -o /dev/null -f