Use the new prcontext script.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@15427 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
John Criswell 2004-08-02 22:31:58 +00:00
parent 955a742569
commit cc455dea0f
16 changed files with 16 additions and 16 deletions

View File

@ -1,4 +1,4 @@
; RUN: llvm-as < %s | opt -constmerge | llvm-dis | grep -C2 foo | grep bar
; RUN: llvm-as < %s | opt -constmerge | llvm-dis | %prcontext foo 2 | grep bar
%foo = constant int 6
%bar = constant int 6

View File

@ -1,4 +1,4 @@
; RUN: llvm-as < %s | opt -indvars | llvm-dis | grep -C1 Loop: | grep %indvar
; RUN: llvm-as < %s | opt -indvars | llvm-dis | %prcontext Loop: 1 | grep %indvar
; The indvar simplification code should ensure that the first PHI in the block
; is the canonical one!

View File

@ -1,7 +1,7 @@
; This test ensures that alloca instructions in the entry block for an inlined
; function are moved to the top of the function they are inlined into.
;
; RUN: llvm-as < %s | opt -inline | llvm-dis | grep -C1 alloca | grep Entry:
; RUN: llvm-as < %s | opt -inline | llvm-dis | %prcontext alloca 1 | grep Entry:
int %func(int %i) {
%X = alloca int

View File

@ -1,7 +1,7 @@
; This testcase tests for a problem where LICM hoists
; potentially trapping instructions when they are not guaranteed to execute.
;
; RUN: llvm-as < %s | opt -licm | llvm-dis | grep -C2 "IfUnEqual" | grep div
; RUN: llvm-as < %s | opt -licm | llvm-dis | %prcontext "IfUnEqual" 2 | grep div
%X = global int 0
declare void %foo()

View File

@ -1,7 +1,7 @@
; This testcase tests to make sure a trapping instruction is hoisted when
; it is guaranteed to execute.
;
; RUN: llvm-as < %s | opt -licm | llvm-dis | grep -C2 "test" | grep div
; RUN: llvm-as < %s | opt -licm | llvm-dis | %prcontext "test" 2 | grep div
%X = global int 0
declare void %foo(int)

View File

@ -1,4 +1,4 @@
; RUN: llvm-as < %s | opt -licm | llvm-dis | grep -C1 volatile | grep Loop
; RUN: llvm-as < %s | opt -licm | llvm-dis | %prcontext volatile 1 | grep Loop
%X = global int 7

View File

@ -1,4 +1,4 @@
; RUN: llvm-as < %s | opt -basicaa -licm | llvm-dis | grep -C1 sin | grep Out:
; RUN: llvm-as < %s | opt -basicaa -licm | llvm-dis | %prcontext sin 1 | grep Out:
declare double %sin(double)
declare void %foo()

View File

@ -1,4 +1,4 @@
; RUN: llvm-as < %s | opt -basicaa -licm | llvm-dis | grep -C1 strlen | grep Out:
; RUN: llvm-as < %s | opt -basicaa -licm | llvm-dis | %prcontext strlen 1 | grep Out:
declare int %strlen(sbyte*)
declare void %foo()

View File

@ -1,7 +1,7 @@
; This testcase checks to make sure the sinker does not cause problems with
; critical edges.
; RUN: llvm-as < %s | opt -licm | llvm-dis | grep -C1 add | grep Exit
; RUN: llvm-as < %s | opt -licm | llvm-dis | %prcontext add 1 | grep Exit
implementation ; Functions:

View File

@ -2,7 +2,7 @@
; the instruction to the exit blocks instead of executing it on every
; iteration of the loop.
;
; RUN: llvm-as < %s | opt -licm | llvm-dis | grep -C1 mul | grep Out:
; RUN: llvm-as < %s | opt -licm | llvm-dis | %prcontext mul 1 | grep Out:
int %test(int %N) {
Entry:

View File

@ -2,7 +2,7 @@
; result of the load is only used outside of the loop, sink the load instead of
; hoisting it!
;
; RUN: llvm-as < %s | opt -licm | llvm-dis | grep -C1 load | grep Out:
; RUN: llvm-as < %s | opt -licm | llvm-dis | %prcontext load 1 | grep Out:
%X = global int 5

View File

@ -3,7 +3,7 @@
; instructions from the loop. Instead they got hoisted, which is better than
; leaving them in the loop, but increases register pressure pointlessly.
; RUN: llvm-as < %s | opt -licm | llvm-dis | grep -C1 getelementptr | grep Out:
; RUN: llvm-as < %s | opt -licm | llvm-dis | %prcontext getelementptr 1 | grep Out:
%Ty = type { int, int }
%X = external global %Ty

View File

@ -1,7 +1,7 @@
; This testcase ensures that we can sink instructions from loops with
; multiple exits.
;
; RUN: llvm-as < %s | opt -licm | llvm-dis | grep -C1 mul | grep 'Out[12]:'
; RUN: llvm-as < %s | opt -licm | llvm-dis | %prcontext mul 1 | grep 'Out[12]:'
int %test(int %N, bool %C) {
Entry:

View File

@ -2,7 +2,7 @@
; some exits out of the loop, and that we can do so without breaking dominator
; info.
;
; RUN: llvm-as < %s | opt -licm | llvm-dis | grep -C1 add | grep exit2:
; RUN: llvm-as < %s | opt -licm | llvm-dis | %prcontext add 1 | grep exit2:
implementation ; Functions:

View File

@ -1,4 +1,4 @@
; RUN: llvm-as < %s | opt -licm | llvm-dis | grep -C1 add | grep preheader.loopexit:
; RUN: llvm-as < %s | opt -licm | llvm-dis | %prcontext add 1 | grep preheader.loopexit:
implementation

View File

@ -1,7 +1,7 @@
; Potentially trapping instructions may be sunk as long as they are guaranteed
; to be executed.
;
; RUN: llvm-as < %s | opt -licm | llvm-dis | grep -C1 div | grep Out:
; RUN: llvm-as < %s | opt -licm | llvm-dis | %prcontext div 1 | grep Out:
int %test(int %N) {
Entry: