maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/polly/test/ScopInfo/NonAffine/non_affine_float_compare.ll

69 lines
2.5 KiB
LLVM
Raw Normal View History

Do not detect Scops with only one loop. If a region does not have more than one loop, we do not identify it as a Scop in ScopDetection. The main optimizations Polly is currently performing (tiling, preparation for outer-loop vectorization and loop fusion) are unlikely to have a positive impact on individual loops. In some cases, Polly's run-time alias checks or conditional hoisting may still have a positive impact, but those are mostly enabling transformations which LLVM already performs for individual loops. As we do not focus on individual loops, we leave them untouched to not introduce compile time regressions and execution time noise. This results in good compile time reduction (oourafft: -73.99%, smg2000: -56.25%). Contributed-by: Pratik Bhatu <cs12b1010@iith.ac.in> Reviewers: grosser Differential Revision: http://reviews.llvm.org/D12268 llvm-svn: 246161
2015-08-28 00:55:18 +08:00
; RUN: opt %loadPolly -polly-scops -polly-allow-nonaffine-branches \
; RUN: -polly-detect-unprofitable -analyze < %s | FileCheck %s
Allow non-affine control flow -- SCoP Modeling This allows us to model non-affine regions in the SCoP representation. SCoP statements can now describe either basic blocks or non-affine regions. In the latter case all accesses in the region are accumulated for the statement and write accesses, except in the entry, have to be marked as may-write. Differential Revision: http://reviews.llvm.org/D7846 llvm-svn: 230329
2015-02-24 20:00:50 +08:00
;
; void f(float *A) {
; for (int i = 0; i < 1024; i++)
; if (A[i] == A[i - 1])
; A[i]++;
; }
;
; CHECK: Function: f
; CHECK: Region: %bb1---%bb14
; CHECK: Max Loop Depth: 1
; CHECK: Statements {
Make non-affine statement names isl compatible Named isl sets can generally have any name if they remain within Polly, but only certain strings can be parsed by isl. The new names we create ensure that we can always copy-past isl strings from Polly to other isl tools, e.g. for debugging. llvm-svn: 241787
2015-07-09 15:31:45 +08:00
; CHECK: Stmt_bb2__TO__bb12
Allow non-affine control flow -- SCoP Modeling This allows us to model non-affine regions in the SCoP representation. SCoP statements can now describe either basic blocks or non-affine regions. In the latter case all accesses in the region are accumulated for the statement and write accesses, except in the entry, have to be marked as may-write. Differential Revision: http://reviews.llvm.org/D7846 llvm-svn: 230329
2015-02-24 20:00:50 +08:00
; CHECK: Domain :=
Traverse the SCoP to compute non-loop-carried domain conditions In order to compute domain conditions for conditionals we will now traverse the region in the ScopInfo once and build the domains for each block in the region. The SCoP statements can then use these constraints when they build their domain. The reason behind this change is twofold: 1) This removes a big chunk of preprocessing logic from the TempScopInfo, namely the Conditionals we used to build there. Additionally to moving this logic it is also simplified. Instead of walking the dominance tree up for each basic block in the region (as we did before), we now traverse the region only once in order to collect the domain conditions. 2) This is the first step towards the isl based domain creation. The second step will traverse the region similar to this step, however it will propagate back edge conditions. Once both are in place this conditional handling will allow multiple exit loops additional logic. Reviewers: grosser Differential Revision: http://reviews.llvm.org/D12428 llvm-svn: 246398
2015-08-31 05:13:53 +08:00
; CHECK: { Stmt_bb2__TO__bb12[i0] :
; CHECK-DAG: i0 >= 0
; CHECK-DAG: and
; CHECK-DAG: i0 <= 1023
; CHECK: }
Rename 'scattering' to 'schedule' In Polly we used both the term 'scattering' and the term 'schedule' to describe the execution order of a statement without actually distinguishing between them. We now uniformly use the term 'schedule' for the execution order. This corresponds to the terminology of isl. History: CLooG introduced the term scattering as the generated code can be used as a sequential execution order (schedule) or as a parallel dimension enumerating different threads of execution (placement). In Polly and/or isl the term placement was never used, but we uniformly refer to an execution order as a schedule and only later introduce parallelism. When doing so we do not talk about about specific placement dimensions. llvm-svn: 235380
2015-04-21 19:37:25 +08:00
; CHECK: Schedule :=
Make non-affine statement names isl compatible Named isl sets can generally have any name if they remain within Polly, but only certain strings can be parsed by isl. The new names we create ensure that we can always copy-past isl strings from Polly to other isl tools, e.g. for debugging. llvm-svn: 241787
2015-07-09 15:31:45 +08:00
; CHECK: { Stmt_bb2__TO__bb12[i0] -> [i0] };
Allow non-affine control flow -- SCoP Modeling This allows us to model non-affine regions in the SCoP representation. SCoP statements can now describe either basic blocks or non-affine regions. In the latter case all accesses in the region are accumulated for the statement and write accesses, except in the entry, have to be marked as may-write. Differential Revision: http://reviews.llvm.org/D7846 llvm-svn: 230329
2015-02-24 20:00:50 +08:00
; CHECK: ReadAccess := [Reduction Type: NONE] [Scalar: 0]
Make non-affine statement names isl compatible Named isl sets can generally have any name if they remain within Polly, but only certain strings can be parsed by isl. The new names we create ensure that we can always copy-past isl strings from Polly to other isl tools, e.g. for debugging. llvm-svn: 241787
2015-07-09 15:31:45 +08:00
; CHECK: { Stmt_bb2__TO__bb12[i0] -> MemRef_A[i0] };
Allow non-affine control flow -- SCoP Modeling This allows us to model non-affine regions in the SCoP representation. SCoP statements can now describe either basic blocks or non-affine regions. In the latter case all accesses in the region are accumulated for the statement and write accesses, except in the entry, have to be marked as may-write. Differential Revision: http://reviews.llvm.org/D7846 llvm-svn: 230329
2015-02-24 20:00:50 +08:00
; CHECK: ReadAccess := [Reduction Type: NONE] [Scalar: 0]
Make non-affine statement names isl compatible Named isl sets can generally have any name if they remain within Polly, but only certain strings can be parsed by isl. The new names we create ensure that we can always copy-past isl strings from Polly to other isl tools, e.g. for debugging. llvm-svn: 241787
2015-07-09 15:31:45 +08:00
; CHECK: { Stmt_bb2__TO__bb12[i0] -> MemRef_A[-1 + i0] };
Allow non-affine control flow -- SCoP Modeling This allows us to model non-affine regions in the SCoP representation. SCoP statements can now describe either basic blocks or non-affine regions. In the latter case all accesses in the region are accumulated for the statement and write accesses, except in the entry, have to be marked as may-write. Differential Revision: http://reviews.llvm.org/D7846 llvm-svn: 230329
2015-02-24 20:00:50 +08:00
; CHECK: ReadAccess := [Reduction Type: NONE] [Scalar: 0]
Make non-affine statement names isl compatible Named isl sets can generally have any name if they remain within Polly, but only certain strings can be parsed by isl. The new names we create ensure that we can always copy-past isl strings from Polly to other isl tools, e.g. for debugging. llvm-svn: 241787
2015-07-09 15:31:45 +08:00
; CHECK: { Stmt_bb2__TO__bb12[i0] -> MemRef_A[i0] };
Allow non-affine control flow -- SCoP Modeling This allows us to model non-affine regions in the SCoP representation. SCoP statements can now describe either basic blocks or non-affine regions. In the latter case all accesses in the region are accumulated for the statement and write accesses, except in the entry, have to be marked as may-write. Differential Revision: http://reviews.llvm.org/D7846 llvm-svn: 230329
2015-02-24 20:00:50 +08:00
; CHECK: MayWriteAccess := [Reduction Type: NONE] [Scalar: 0]
Make non-affine statement names isl compatible Named isl sets can generally have any name if they remain within Polly, but only certain strings can be parsed by isl. The new names we create ensure that we can always copy-past isl strings from Polly to other isl tools, e.g. for debugging. llvm-svn: 241787
2015-07-09 15:31:45 +08:00
; CHECK: { Stmt_bb2__TO__bb12[i0] -> MemRef_A[i0] };
Allow non-affine control flow -- SCoP Modeling This allows us to model non-affine regions in the SCoP representation. SCoP statements can now describe either basic blocks or non-affine regions. In the latter case all accesses in the region are accumulated for the statement and write accesses, except in the entry, have to be marked as may-write. Differential Revision: http://reviews.llvm.org/D7846 llvm-svn: 230329
2015-02-24 20:00:50 +08:00
; CHECK: }
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
define void @f(float* %A) {
bb:
br label %bb1
bb1: ; preds = %bb13, %bb
%indvars.iv = phi i64 [ %indvars.iv.next, %bb13 ], [ 0, %bb ]
%exitcond = icmp ne i64 %indvars.iv, 1024
br i1 %exitcond, label %bb2, label %bb14
bb2: ; preds = %bb1
Update Polly tests to handle explicitly typed gep changes in LLVM llvm-svn: 230784
2015-02-28 03:20:19 +08:00
%tmp = getelementptr inbounds float, float* %A, i64 %indvars.iv
Update Polly tests to handle explicitly typed load changes in LLVM. llvm-svn: 230796
2015-02-28 05:22:50 +08:00
%tmp3 = load float, float* %tmp, align 4
Allow non-affine control flow -- SCoP Modeling This allows us to model non-affine regions in the SCoP representation. SCoP statements can now describe either basic blocks or non-affine regions. In the latter case all accesses in the region are accumulated for the statement and write accesses, except in the entry, have to be marked as may-write. Differential Revision: http://reviews.llvm.org/D7846 llvm-svn: 230329
2015-02-24 20:00:50 +08:00
%tmp4 = add nsw i64 %indvars.iv, -1
Update Polly tests to handle explicitly typed gep changes in LLVM llvm-svn: 230784
2015-02-28 03:20:19 +08:00
%tmp5 = getelementptr inbounds float, float* %A, i64 %tmp4
Update Polly tests to handle explicitly typed load changes in LLVM. llvm-svn: 230796
2015-02-28 05:22:50 +08:00
%tmp6 = load float, float* %tmp5, align 4
Allow non-affine control flow -- SCoP Modeling This allows us to model non-affine regions in the SCoP representation. SCoP statements can now describe either basic blocks or non-affine regions. In the latter case all accesses in the region are accumulated for the statement and write accesses, except in the entry, have to be marked as may-write. Differential Revision: http://reviews.llvm.org/D7846 llvm-svn: 230329
2015-02-24 20:00:50 +08:00
%tmp7 = fcmp oeq float %tmp3, %tmp6
br i1 %tmp7, label %bb8, label %bb12
bb8: ; preds = %bb2
Update Polly tests to handle explicitly typed gep changes in LLVM llvm-svn: 230784
2015-02-28 03:20:19 +08:00
%tmp9 = getelementptr inbounds float, float* %A, i64 %indvars.iv
Update Polly tests to handle explicitly typed load changes in LLVM. llvm-svn: 230796
2015-02-28 05:22:50 +08:00
%tmp10 = load float, float* %tmp9, align 4
Allow non-affine control flow -- SCoP Modeling This allows us to model non-affine regions in the SCoP representation. SCoP statements can now describe either basic blocks or non-affine regions. In the latter case all accesses in the region are accumulated for the statement and write accesses, except in the entry, have to be marked as may-write. Differential Revision: http://reviews.llvm.org/D7846 llvm-svn: 230329
2015-02-24 20:00:50 +08:00
%tmp11 = fadd float %tmp10, 1.000000e+00
store float %tmp11, float* %tmp9, align 4
br label %bb12
bb12: ; preds = %bb8, %bb2
br label %bb13
bb13: ; preds = %bb12
%indvars.iv.next = add nuw nsw i64 %indvars.iv, 1
br label %bb1
bb14: ; preds = %bb1
ret void
}