force evaluation (ComputeIterationCountExhaustively) should be turned off.
It doesn't apply to trip-count2.ll because this file tests the brute force
evaluation.
The test for PR2364 (2008-05-25-NegativeStepToZero.ll) currently fails
showing that the patch for this bug doesn't work. I'll fix it in a few hours
with a patch for PR2088.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@53792
91177308-0d34-0410-b5e6-
96231b3b80d8
-; RUN: llvm-as < %s | opt -analyze -scalar-evolution | grep {Loop bb: 100 iterations}
+; RUN: llvm-as < %s | opt -analyze -scalar-evolution \
+; RUN: -scalar-evolution-max-iterations=0 | grep {Loop bb: 100 iterations}
; PR1533
@array = weak global [101 x i32] zeroinitializer, align 32 ; <[100 x i32]*> [#uses=1]
-; RUN: llvm-as < %s | opt -analyze -scalar-evolution | grep {13 iterations}
+; RUN: llvm-as < %s | opt -analyze -scalar-evolution \
+; RUN: -scalar-evolution-max-iterations=0 | grep {13 iterations}
; PR1706
define i32 @f() {
-; RUN: llvm-as < %s | opt -analyze -scalar-evolution | grep {61 iterations}
+; RUN: llvm-as < %s | opt -analyze -scalar-evolution \
+; RUN: -scalar-evolution-max-iterations=0 | grep {61 iterations}
; PR2364
define i32 @func_6() nounwind {
-; RUN: llvm-as < %s | opt -analyze -scalar-evolution | \
-; RUN: grep {100 iterations}
+; RUN: llvm-as < %s | opt -analyze -scalar-evolution \
+; RUN: -scalar-evolution-max-iterations=0 | grep {100 iterations}
; PR1101
@A = weak global [1000 x i32] zeroinitializer, align 32
-; RUN: llvm-as < %s | opt -analyze -scalar-evolution | \
-; RUN: grep {10000 iterations}
+; RUN: llvm-as < %s | opt -analyze -scalar-evolution \
+; RUN: -scalar-evolution-max-iterations=0 | grep {10000 iterations}
; PR1101
@A = weak global [1000 x i32] zeroinitializer, align 32