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/read-only-scalar-used-in-ph...

62 lines
2.2 KiB
LLVM
Raw Normal View History

tests: Drop -polly-detect-unprofitable and -polly-no-early-exit These flags are now always passed to all tests and need to be disabled if not needed. Disabling these flags, rather than passing them to almost all tests, significantly simplfies our RUN: lines. llvm-svn: 249422
2015-10-06 23:36:44 +08:00
; RUN: opt %loadPolly -analyze -polly-scops \
Handle read-only scalars used in PHI-nodes correctly This change addresses three issues: - Read only scalars that enter a PHI node through an edge that comes from outside the scop are not modeled any more, as such PHI nodes will always be initialized to this initial value right before the SCoP is entered. - For PHI nodes that depend on a scalar value that is defined outside the scop, but where the scalar values is passed through an edge that itself comes from a BB that is part of the region, we introduce in this basic block a read of the out-of-scop value to ensure it's value is available to write it into the PHI alloc location. - Read only uses of scalars by PHI nodes are ignored in the general read only handling code, as they are taken care of by the general PHI node modeling code. llvm-svn: 248535
2015-09-25 04:59:59 +08:00
; RUN: < %s | FileCheck %s
;
; float foo(float sum, float A[]) {
;
; for (long i = 0; i < 100; i++)
; sum += A[i];
;
; return sum;
; }
Prepare unit tests for update to ISL 0.16 ISL 0.16 will change how sets are printed which breaks 117 unit tests that text-compare printed sets. This patch re-formats most of these unit tests using a script and small manual editing on top of that. When actually updating ISL, most work is done by just re-running the script to adapt to the changed output. Some tests that compare IR and tests with single CHECK-lines that can be easily updated manually are not included here. The re-format script will also be committed afterwards. The per-test formatter invocation command lines options will not be added in the near future because it is ad hoc and would overwrite the manual edits. Ideally it also shouldn't be required anymore because ISL's set printing has become more stable in 0.16. Differential Revision: http://reviews.llvm.org/D16095 llvm-svn: 257851
2016-01-15 08:48:42 +08:00
; CHECK: Statements {
; CHECK-NEXT: Stmt_next
; CHECK-NEXT: Domain :=
; CHECK-NEXT: { Stmt_next[] };
; CHECK-NEXT: Schedule :=
; CHECK-NEXT: { Stmt_next[] -> [0, 0] };
; CHECK-NEXT: ReadAccess := [Reduction Type: NONE] [Scalar: 1]
; CHECK-NEXT: { Stmt_next[] -> MemRef_sum[] };
; CHECK-NEXT: MustWriteAccess := [Reduction Type: NONE] [Scalar: 1]
; CHECK-NEXT: { Stmt_next[] -> MemRef_phisum__phi[] };
; CHECK-NEXT: MustWriteAccess := [Reduction Type: NONE] [Scalar: 1]
; CHECK-NEXT: { Stmt_next[] -> MemRef_phisummerge[] };
; CHECK-NEXT: Stmt_bb1
; CHECK-NEXT: Domain :=
Update to ISL 0.16.1 llvm-svn: 257898
2016-01-15 23:54:45 +08:00
; CHECK-NEXT: { Stmt_bb1[i0] : 0 <= i0 <= 100 };
Prepare unit tests for update to ISL 0.16 ISL 0.16 will change how sets are printed which breaks 117 unit tests that text-compare printed sets. This patch re-formats most of these unit tests using a script and small manual editing on top of that. When actually updating ISL, most work is done by just re-running the script to adapt to the changed output. Some tests that compare IR and tests with single CHECK-lines that can be easily updated manually are not included here. The re-format script will also be committed afterwards. The per-test formatter invocation command lines options will not be added in the near future because it is ad hoc and would overwrite the manual edits. Ideally it also shouldn't be required anymore because ISL's set printing has become more stable in 0.16. Differential Revision: http://reviews.llvm.org/D16095 llvm-svn: 257851
2016-01-15 08:48:42 +08:00
; CHECK-NEXT: Schedule :=
; CHECK-NEXT: { Stmt_bb1[i0] -> [1, i0] };
; CHECK-NEXT: MustWriteAccess := [Reduction Type: NONE] [Scalar: 1]
; CHECK-NEXT: { Stmt_bb1[i0] -> MemRef_phisum__phi[] };
; CHECK-NEXT: ReadAccess := [Reduction Type: NONE] [Scalar: 1]
; CHECK-NEXT: { Stmt_bb1[i0] -> MemRef_phisum__phi[] };
; CHECK-NEXT: ReadAccess := [Reduction Type: NONE] [Scalar: 0]
; CHECK-NEXT: { Stmt_bb1[i0] -> MemRef_A[i0] };
; CHECK-NEXT: MustWriteAccess := [Reduction Type: NONE] [Scalar: 1]
; CHECK-NEXT: { Stmt_bb1[i0] -> MemRef_phisummerge[] };
; CHECK-NEXT: }
Handle read-only scalars used in PHI-nodes correctly This change addresses three issues: - Read only scalars that enter a PHI node through an edge that comes from outside the scop are not modeled any more, as such PHI nodes will always be initialized to this initial value right before the SCoP is entered. - For PHI nodes that depend on a scalar value that is defined outside the scop, but where the scalar values is passed through an edge that itself comes from a BB that is part of the region, we introduce in this basic block a read of the out-of-scop value to ensure it's value is available to write it into the PHI alloc location. - Read only uses of scalars by PHI nodes are ignored in the general read only handling code, as they are taken care of by the general PHI node modeling code. llvm-svn: 248535
2015-09-25 04:59:59 +08:00
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
define float @foo(float %sum, float* %A) {
bb:
br label %next
next:
br i1 true, label %bb1, label %bb7
bb1:
%i = phi i64 [ 0, %next ], [ %i.next, %bb1 ]
%phisum = phi float [ %sum, %next ], [ %tmp5, %bb1 ]
%tmp = getelementptr inbounds float, float* %A, i64 %i
%tmp4 = load float, float* %tmp, align 4
%tmp5 = fadd float %phisum, %tmp4
%i.next = add nuw nsw i64 %i, 1
%exitcond = icmp ne i64 %i, 100
br i1 %exitcond, label %bb1, label %bb7
bb7:
Add missing PHI to test case llvm-svn: 248563
2015-09-25 13:41:30 +08:00
%phisummerge = phi float [%phisum, %bb1], [0.0, %next]
ret float %phisummerge
Handle read-only scalars used in PHI-nodes correctly This change addresses three issues: - Read only scalars that enter a PHI node through an edge that comes from outside the scop are not modeled any more, as such PHI nodes will always be initialized to this initial value right before the SCoP is entered. - For PHI nodes that depend on a scalar value that is defined outside the scop, but where the scalar values is passed through an edge that itself comes from a BB that is part of the region, we introduce in this basic block a read of the out-of-scop value to ensure it's value is available to write it into the PHI alloc location. - Read only uses of scalars by PHI nodes are ignored in the general read only handling code, as they are taken care of by the general PHI node modeling code. llvm-svn: 248535
2015-09-25 04:59:59 +08:00
}