llvm/test/Transforms/LoopStrengthReduce/ephemeral.ll
Jingyue Wu 8e7e3650af [LSR] don't attempt to promote ephemeral values to indvars
Summary:
This at least saves compile time. I also encountered a case where
ephemeral values affect whether other variables are promoted, causing
performance issues. It may be a bug in LSR, but I didn't manage to
reduce it yet. Anyhow, I believe it's in general not worth considering
ephemeral values in LSR.

Reviewers: atrick, hfinkel

Subscribers: llvm-commits

Differential Revision: http://reviews.llvm.org/D11115

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@242011 91177308-0d34-0410-b5e6-96231b3b80d8
2015-07-13 03:28:53 +00:00

42 lines
898 B
LLVM

; RUN: opt < %s -loop-reduce -S | FileCheck %s
target datalayout = "e-i64:64-v16:16-v32:32-n16:32:64"
; for (int i = 0; i < n; ++i) {
; use(i * 5 + 3);
; // i * a + b is ephemeral and shouldn't be promoted by LSR
; __builtin_assume(i * a + b >= 0);
; }
define void @ephemeral(i32 %a, i32 %b, i32 %n) {
; CHECK-LABEL: @ephemeral(
entry:
br label %loop
loop:
%i = phi i32 [ 0, %entry ], [ %inc, %loop ]
; Only i and i * 5 + 3 should be indvars, not i * a + b.
; CHECK: phi i32
; CHECK: phi i32
; CHECK-NOT: phi i32
%inc = add nsw i32 %i, 1
%exitcond = icmp eq i32 %inc, %n
%0 = mul nsw i32 %i, 5
%1 = add nsw i32 %0, 3
call void @use(i32 %1)
%2 = mul nsw i32 %i, %a
%3 = add nsw i32 %2, %b
%4 = icmp sgt i32 %3, -1
call void @llvm.assume(i1 %4)
br i1 %exitcond, label %exit, label %loop
exit:
ret void
}
declare void @use(i32)
declare void @llvm.assume(i1)