maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/polly/test/Isl/CodeGen/scalar-references-used-in-s...

52 lines
1.4 KiB
LLVM
Raw Normal View History

ScopDetection: Only detect scops that have at least one read and one write Scops that only read seem generally uninteresting and scops that only write are most likely initializations where there is also little to optimize. To not waste compile time we bail early. Differential Revision: http://reviews.llvm.org/D7735 llvm-svn: 229820
2015-02-19 13:31:07 +08:00
; RUN: opt %loadPolly -polly-detect-unprofitable -polly-no-early-exit -polly-codegen-isl -S < %s | FileCheck %s
BlockGenerator: Recompute values from SCEV before handing back the original values This patch moves the SCEV based (re)generation of values before the checking for scop-constant terms. It enables us to provide SCEV based replacements, which are necessary to correctly generate OpenMP subfunctions when using the SCEV based code generation. When recomputing a new value for a value used in the code of the original scop, we previously directly returned the same original value for all scop-constant expressions without even trying to regenerate these values using our SCEV expression. This is correct when the newly generated code remains fully in the same function, however in case we want to outline parts of the newly generated scop into subfunctions, this approach means we do not have any opportunity to update these values in the SCEV based code generation. (In the non-SCEV based code generation, we can provide such updates through the GlobalMap). To ensure we have this opportunity, we first try to regenerate scalar terms with our SCEV builder and will only return scop-constant expressions if SCEV based code generation was not possible. This change should not affect the results of the existing code generation passes. It only impacts the upcoming OpenMP based code generation. This commit also adds a test case. This test case passes before and after this commit. It was added to ensure test coverage for the changed code. llvm-svn: 221393
2014-11-06 04:48:56 +08:00
; Test the code generation in the presence of a scalar out-of-scop value being
; used from within the SCoP.
; CHECH-LABEL: @scalar-function-argument
; CHECK: polly.split_new_and_old
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
define void @scalar-function-argument(float* %A, float %sqrinv) {
entry:
br label %for.body
for.body:
%indvar = phi i64 [ %indvar.next, %for.body ], [ 0, %entry ]
%mul104 = fmul float 1.0, %sqrinv
%rp107 = getelementptr float* %A, i64 %indvar
store float %mul104, float* %rp107, align 4
%indvar.next = add nsw i64 %indvar, 1
%cmp = icmp slt i64 1024, %indvar.next
br i1 %cmp, label %for.end, label %for.body
for.end:
ret void
}
; CHECH-LABEL: @scalar-outside-of-scop
; CHECK: polly.split_new_and_old
define void @scalar-outside-of-scop(float* %A) {
entry:
%sqrinv = call float @getFloat()
br label %for.body
for.body:
%indvar = phi i64 [ %indvar.next, %for.body ], [ 0, %entry ]
%mul104 = fmul float 1.0, %sqrinv
%rp107 = getelementptr float* %A, i64 %indvar
store float %mul104, float* %rp107, align 4
%indvar.next = add nsw i64 %indvar, 1
%cmp = icmp slt i64 1024, %indvar.next
br i1 %cmp, label %for.end, label %for.body
for.end:
ret void
}
declare float @getFloat()