diff options
| author | Tom Stellard <tstellar@redhat.com> | 2017-05-30 14:51:27 +0000 |
|---|---|---|
| committer | Tom Stellard <tstellar@redhat.com> | 2017-05-30 14:51:27 +0000 |
| commit | e47a2cdbdfc008ef83a2cba4af342e745f9a48b0 (patch) | |
| tree | 2e4d3dffe398b04fba432e9dbf607162637667eb | |
| parent | 3160d12317fef55091280045002ed7a5f7472f53 (diff) | |
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?
------------------------------------------------------------------------
llvm-svn: 304213
| -rw-r--r-- | polly/test/ScopInfo/invariant_load_zext_parameter-2.ll | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/polly/test/ScopInfo/invariant_load_zext_parameter-2.ll b/polly/test/ScopInfo/invariant_load_zext_parameter-2.ll index d2cb200d990b..396828e23609 100644 --- a/polly/test/ScopInfo/invariant_load_zext_parameter-2.ll +++ b/polly/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. ; |