Changed all of these tests to be TestRunner tests (or, at least they can be

TestRunner tests).
This makes creating the new test database class easier to implement.

llvm-svn: 8841
This commit is contained in:
John Criswell 2003-10-03 18:42:25 +00:00
parent 101d5058cb
commit 8a261626fc
13 changed files with 24 additions and 4 deletions

View File

@ -2,6 +2,8 @@
; folded completely away if possible. This is a very common case, so it should
; be efficient.
;
; RUN: analyze %s -tddatastructure
;
implementation
sbyte* %merge1([100 x sbyte] *%A, long %N) {

View File

@ -1,4 +1,5 @@
;
; RUN: analyze %s -tddatastructure
%crazy = type [2 x { [2 x sbyte], short } ]
implementation

View File

@ -1,4 +1,6 @@
; This file contains a list of situations where node folding should happen...
;
; RUN: analyze %s -tddatastructure
implementation

View File

@ -1,5 +1,6 @@
; very simple test
;
; RUN: analyze %s -tddatastructure
implementation

View File

@ -1,3 +1,5 @@
;
; RUN: analyze %s -tddatastructure
%str = type { int*, int* }

View File

@ -1,5 +1,7 @@
; This file contains a list of cases where node folding should NOT happen
;
; RUN: analyze %s -tddatastructure
;
implementation

View File

@ -1,3 +1,6 @@
;
; RUN: analyze %s -tddatastructure
%G = global int 2 ; <int*> [#uses=1]
%H = global int* null

View File

@ -1,4 +1,5 @@
;
; RUN: analyze %s -tddatastructure
int* %test1(int *%A) {
%R = getelementptr int* %A, long 1

View File

@ -1,5 +1,7 @@
; A test for "physical subtyping" used in some C programs...
;
; RUN: analyze %s -tddatastructure
;
%ST = type { int, int* } ; "Subtype"
%DT = type { int, int*, int } ; "derived type"

View File

@ -1,3 +1,5 @@
; RUN: analyze %s -tddatastructure
implementation ; Functions:
declare void %__main()

View File

@ -1,4 +1,4 @@
; RUN: analyze %s -tddatastructure
void %foo(int* %X) {
store int 4, int* %X

View File

@ -1,3 +1,4 @@
; RUN: analyze %s -tddatastructure
implementation

View File

@ -1,3 +1,4 @@
; RUN: analyze %s -tddatastructure
%str = type { int, int* }