The BLX instruction is encoded differently than the BL, because why not? In

[oota-llvm.git] / test / Analysis / ScalarEvolution / 2008-11-18-Stride2.ll

diff --git a/test/Analysis/ScalarEvolution/2008-11-18-Stride2.ll b/test/Analysis/ScalarEvolution/2008-11-18-Stride2.ll
index 4a76970ce19adf8632082e9ccfb7ea0ddb5595d4..fa9f21af3713e4563231a5fc0fe4829064ee230b 100644 (file)
--- a/test/Analysis/ScalarEvolution/2008-11-18-Stride2.ll
+++ b/test/Analysis/ScalarEvolution/2008-11-18-Stride2.ll
@@ -1,6 +1,9 @@
-; RUN: llvm-as < %s | opt -analyze -scalar-evolution |& grep {/u 3}
+; RUN: opt < %s -analyze -scalar-evolution |& grep {/u 3}
 ; XFAIL: *
 
+; This is a tricky testcase for unsigned wrap detection which ScalarEvolution
+; doesn't yet know how to do.
+
 define i32 @f(i32 %x) nounwind readnone {
 entry:
        %0 = icmp ugt i32 %x, 999               ; <i1> [#uses=1]