[polly] r315912 - [Polly] Add XFAIL to large-numbers-in-boundary-context.ll

Anna Thomas via llvm-commits llvm-commits at lists.llvm.org
Mon Oct 16 08:12:39 PDT 2017


Author: annat
Date: Mon Oct 16 08:12:39 2017
New Revision: 315912

URL: http://llvm.org/viewvc/llvm-project?rev=315912&view=rev
Log:
[Polly] Add XFAIL to large-numbers-in-boundary-context.ll

After rL315683 (improve SCEV to calculate max BETakenCount when end
bound of loop is variant and loop is of form {Start,+1, Stride} LT End)
this test in polly started failing.
However, as discussed in https://reviews.llvm.org/rL315683,
this polly test is not a loops bound test and the MaxBECount calculated by
SCEV looks correct. The max BECount is the value calculated even when the end
bound of loop is invariant.

As discussed with Tobias offline, I'm marking this as an XFAIL, until he
gets a chance to update the testcase, so the build bot goes to green.

Modified:
    polly/trunk/test/Isl/CodeGen/large-numbers-in-boundary-context.ll

Modified: polly/trunk/test/Isl/CodeGen/large-numbers-in-boundary-context.ll
URL: http://llvm.org/viewvc/llvm-project/polly/trunk/test/Isl/CodeGen/large-numbers-in-boundary-context.ll?rev=315912&r1=315911&r2=315912&view=diff
==============================================================================
--- polly/trunk/test/Isl/CodeGen/large-numbers-in-boundary-context.ll (original)
+++ polly/trunk/test/Isl/CodeGen/large-numbers-in-boundary-context.ll Mon Oct 16 08:12:39 2017
@@ -1,4 +1,5 @@
 ; RUN: opt %loadPolly -S -polly-codegen < %s | FileCheck %s
+; XFAIL: *
 ;
 ; The boundary context contains a constant that does not fit in 64 bits. Hence,
 ; make sure we bail out. On certain systems, e.g. AOSP, no runtime support for




More information about the llvm-commits mailing list