summaryrefslogtreecommitdiff
path: root/test/Analysis/ScalarEvolution/2008-11-18-Stride1.ll
diff options
context:
space:
mode:
authorAndrew Trick <atrick@apple.com>2013-11-06 02:08:26 +0000
committerAndrew Trick <atrick@apple.com>2013-11-06 02:08:26 +0000
commit10bb82e54fc0608e6220581bda0405af8f12d32f (patch)
treeab801afa3b6055ed52395dfc036d05e48126bbc1 /test/Analysis/ScalarEvolution/2008-11-18-Stride1.ll
parentc86cf046501035b9b931bb2a86ed7b81b8fa9847 (diff)
downloadllvm-10bb82e54fc0608e6220581bda0405af8f12d32f.tar.gz
llvm-10bb82e54fc0608e6220581bda0405af8f12d32f.tar.bz2
llvm-10bb82e54fc0608e6220581bda0405af8f12d32f.tar.xz
Rewrite SCEV's backedge taken count computation.
Patch by Michele Scandale! Rewrite of the functions used to compute the backedge taken count of a loop on LT and GT comparisons. I decided to split the handling of LT and GT cases becasue the trick "a > b == -a < -b" in some cases prevents the trip count computation due to the multiplication by -1 on the two operands of the comparison. This issue comes from the conservative computation of value range of SCEVs: taking the negative SCEV of an expression that have a small positive range (e.g. [0,31]), we would have a SCEV with a fullset as value range. Indeed, in the new rewritten function I tried to better handle the maximum backedge taken count computation when MAX/MIN expression are used to handle the cases where no entry guard is found. Some test have been modified in order to check the new value correctly (I manually check them and reasoning on possible overflow the new values seem correct). I finally added a new test case related to the multiplication by -1 issue on GT comparisons. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@194116 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/Analysis/ScalarEvolution/2008-11-18-Stride1.ll')
-rw-r--r--test/Analysis/ScalarEvolution/2008-11-18-Stride1.ll4
1 files changed, 3 insertions, 1 deletions
diff --git a/test/Analysis/ScalarEvolution/2008-11-18-Stride1.ll b/test/Analysis/ScalarEvolution/2008-11-18-Stride1.ll
index 74698795ca..7acf90c733 100644
--- a/test/Analysis/ScalarEvolution/2008-11-18-Stride1.ll
+++ b/test/Analysis/ScalarEvolution/2008-11-18-Stride1.ll
@@ -1,6 +1,8 @@
; RUN: opt < %s -analyze -scalar-evolution | FileCheck %s
-; CHECK: Loop %bb: Unpredictable backedge-taken count.
+; CHECK: Loop %bb: backedge-taken count is ((-5 + %x) /u 3)
+; CHECK: Loop %bb: max backedge-taken count is 1431655764
+
; ScalarEvolution can't compute a trip count because it doesn't know if
; dividing by the stride will have a remainder. This could theoretically