Unlike a lot of NEON instructions, vext isn't _actually_ parameterized by element...

[oota-llvm.git] / test / Feature / opaquetypes.ll

diff --git a/test/Feature/opaquetypes.ll b/test/Feature/opaquetypes.ll
index 271493f222acacc7b2a579ddaf9b611a42e70ac1..6539c1a6e1ca015a11a2fbf528bd4f2438477c84 100644 (file)
--- a/test/Feature/opaquetypes.ll
+++ b/test/Feature/opaquetypes.ll
@@ -1,11 +1,14 @@
+; RUN: llvm-as < %s | llvm-dis > %t1.ll
+; RUN: llvm-as %t1.ll -o - | llvm-dis > %t2.ll
+; RUN: diff %t1.ll %t2.ll
+
 ; This test case is used to test opaque type processing, forward references,
 ; and recursive types.  Oh my.
 ; 
 
-%SQ1 = type { int }
-%ITy = type opaque
+%SQ1 = type { i32 }
 %SQ2 = type { %ITy }
-%ITy = type int
+%ITy = type i32
 
 
 %CCC = type { \2* }
@@ -18,11 +21,10 @@ type %BBB
 %Composite = type { %0, %1 }
 
 ; Test simple opaque type resolution...
-%intty = type opaque
-%intty = type int
+%intty = type i32
 
 ; Perform a simple forward reference...
-%ty1 = type { %ty2, int }
+%ty1 = type { %ty2, i32 }
 %ty2 = type float
 
 ; Do a recursive type...
@@ -51,7 +53,3 @@ type %BBB
 %Y1 = type { { \3 * }, \2 * }
 %Z1 = type { { \3 * }, [12x\3] *, { { { \5 * } } } }
 
-implementation
-
-
-