From b641a905292c644c783a08fba3fc39ef950c8689 Mon Sep 17 00:00:00 2001 From: Sanjoy Das Date: Mon, 6 Mar 2017 01:12:16 +0000 Subject: [PATCH] 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: 296994 --- polly/test/ScopInfo/invariant_load_zext_parameter-2.ll | 4 ++-- 1 file 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. ;