Merging r296994:
------------------------------------------------------------------------
r296994 | sanjoy | 2017-03-05 20:12:16 -0500 (Sun, 05 Mar 2017) | 10 lines
Adapt to llvm change r296992 to unbreak the bots
r296992 made ScalarEvolution's CompareValueComplexity less aggressive,
and that broke the polly test being fixed in this change. This change
explicitly bumps CompareValueComplexity in said test case to make it
pass.
Can someone from the polly team please can give me an idea on if this
case is important enough to have
scalar-evolution-max-value-compare-depth be 3 by default?
------------------------------------------------------------------------
git-svn-id: https://llvm.org/svn/llvm-project/polly/branches/release_40@304213 91177308-0d34-0410-b5e6-96231b3b80d8
diff --git a/test/ScopInfo/invariant_load_zext_parameter-2.ll b/test/ScopInfo/invariant_load_zext_parameter-2.ll
index d2cb200..396828e 100644
--- a/test/ScopInfo/invariant_load_zext_parameter-2.ll
+++ b/test/ScopInfo/invariant_load_zext_parameter-2.ll
@@ -1,5 +1,5 @@
-; RUN: opt %loadPolly -polly-scops -polly-invariant-load-hoisting=true -analyze < %s | FileCheck %s
-; RUN: opt %loadPolly -polly-codegen -polly-invariant-load-hoisting=true -analyze < %s
+; RUN: opt %loadPolly -scalar-evolution-max-value-compare-depth=3 -polly-scops -polly-invariant-load-hoisting=true -analyze < %s | FileCheck %s
+; RUN: opt %loadPolly -scalar-evolution-max-value-compare-depth=3 -polly-codegen -polly-invariant-load-hoisting=true -analyze < %s
;
; Stress test for the code generation of invariant accesses.
;
