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/non-affine-subregion-domina...

76 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-codegen -S -verify-dom-info \
; RUN: -polly-detect-unprofitable < %s | FileCheck %s
[FIX] Teach RegionGenerator to respect and update dominance When we generate code for a whole region we have to respect dominance and update it too. The first is achieved with multiple "BBMap"s. Each copied block in the region gets its own map. It is initialized only with values mapped in the immediate dominator block, if this block is in the region and was therefor already copied. This way no values defined in a block that doesn't dominate the current one will be used. To update dominance information we check if the immediate dominator of the original block we want to copy is in the region. If so we set the immediate dominator of the current block to the copy of the immediate dominator of the original block. llvm-svn: 230774
2015-02-28 02:29:04 +08:00
;
; Check that we do not reuse the B[i-1] GEP created in block S again in
; block Q. Hence, we create two GEPs for B[i-1]:
;
Update one test I missed when updating for the opaque pointer gep changes to LLVM. llvm-svn: 230792
2015-02-28 04:43:19 +08:00
; CHECK: %scevgep{{.}} = getelementptr i32, i32* %B, i64 -1
; CHECK: %scevgep{{.}} = getelementptr i32, i32* %B, i64 -1
[FIX] Teach RegionGenerator to respect and update dominance When we generate code for a whole region we have to respect dominance and update it too. The first is achieved with multiple "BBMap"s. Each copied block in the region gets its own map. It is initialized only with values mapped in the immediate dominator block, if this block is in the region and was therefor already copied. This way no values defined in a block that doesn't dominate the current one will be used. To update dominance information we check if the immediate dominator of the original block we want to copy is in the region. If so we set the immediate dominator of the current block to the copy of the immediate dominator of the original block. llvm-svn: 230774
2015-02-28 02:29:04 +08:00
;
; void f(int *A, int *B) {
; int x = 0;
; for (int i = 0; i < 1024; i++) {
; if (A[i]) {
; if (i > 512)
; S: A[i] = B[i - 1];
; Q: A[i] += B[i - 1];
; }
; }
; }
;
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
define void @f(i32* %A, i32* %B) {
bb:
br label %bb1
bb1: ; preds = %bb22, %bb
%indvars.iv = phi i64 [ %indvars.iv.next, %bb22 ], [ 0, %bb ]
%exitcond = icmp ne i64 %indvars.iv, 1024
br i1 %exitcond, label %bb2, label %bb23
bb2: ; preds = %bb1
Update one test I missed when updating for the opaque pointer gep changes to LLVM. llvm-svn: 230792
2015-02-28 04:43:19 +08:00
%tmp = getelementptr inbounds i32, i32* %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 i32, i32* %tmp, align 4
[FIX] Teach RegionGenerator to respect and update dominance When we generate code for a whole region we have to respect dominance and update it too. The first is achieved with multiple "BBMap"s. Each copied block in the region gets its own map. It is initialized only with values mapped in the immediate dominator block, if this block is in the region and was therefor already copied. This way no values defined in a block that doesn't dominate the current one will be used. To update dominance information we check if the immediate dominator of the original block we want to copy is in the region. If so we set the immediate dominator of the current block to the copy of the immediate dominator of the original block. llvm-svn: 230774
2015-02-28 02:29:04 +08:00
%tmp4 = icmp eq i32 %tmp3, 0
br i1 %tmp4, label %bb21, label %bb5
bb5: ; preds = %bb2
%tmp6 = icmp sgt i64 %indvars.iv, 512
br i1 %tmp6, label %bb7, label %bb13
bb7: ; preds = %bb5
br label %bb8
bb8: ; preds = %bb7
%tmp9 = add nsw i64 %indvars.iv, -1
Update one test I missed when updating for the opaque pointer gep changes to LLVM. llvm-svn: 230792
2015-02-28 04:43:19 +08:00
%tmp10 = getelementptr inbounds i32, i32* %B, i64 %tmp9
Update Polly tests to handle explicitly typed load changes in LLVM. llvm-svn: 230796
2015-02-28 05:22:50 +08:00
%tmp11 = load i32, i32* %tmp10, align 4
Update one test I missed when updating for the opaque pointer gep changes to LLVM. llvm-svn: 230792
2015-02-28 04:43:19 +08:00
%tmp12 = getelementptr inbounds i32, i32* %A, i64 %indvars.iv
[FIX] Teach RegionGenerator to respect and update dominance When we generate code for a whole region we have to respect dominance and update it too. The first is achieved with multiple "BBMap"s. Each copied block in the region gets its own map. It is initialized only with values mapped in the immediate dominator block, if this block is in the region and was therefor already copied. This way no values defined in a block that doesn't dominate the current one will be used. To update dominance information we check if the immediate dominator of the original block we want to copy is in the region. If so we set the immediate dominator of the current block to the copy of the immediate dominator of the original block. llvm-svn: 230774
2015-02-28 02:29:04 +08:00
store i32 %tmp11, i32* %tmp12, align 4
br label %bb13
bb13: ; preds = %bb8, %bb5
br label %bb14
bb14: ; preds = %bb13
%tmp15 = add nsw i64 %indvars.iv, -1
Update one test I missed when updating for the opaque pointer gep changes to LLVM. llvm-svn: 230792
2015-02-28 04:43:19 +08:00
%tmp16 = getelementptr inbounds i32, i32* %B, i64 %tmp15
Update Polly tests to handle explicitly typed load changes in LLVM. llvm-svn: 230796
2015-02-28 05:22:50 +08:00
%tmp17 = load i32, i32* %tmp16, align 4
Update one test I missed when updating for the opaque pointer gep changes to LLVM. llvm-svn: 230792
2015-02-28 04:43:19 +08:00
%tmp18 = getelementptr inbounds i32, i32* %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
%tmp19 = load i32, i32* %tmp18, align 4
[FIX] Teach RegionGenerator to respect and update dominance When we generate code for a whole region we have to respect dominance and update it too. The first is achieved with multiple "BBMap"s. Each copied block in the region gets its own map. It is initialized only with values mapped in the immediate dominator block, if this block is in the region and was therefor already copied. This way no values defined in a block that doesn't dominate the current one will be used. To update dominance information we check if the immediate dominator of the original block we want to copy is in the region. If so we set the immediate dominator of the current block to the copy of the immediate dominator of the original block. llvm-svn: 230774
2015-02-28 02:29:04 +08:00
%tmp20 = add nsw i32 %tmp19, %tmp17
store i32 %tmp20, i32* %tmp18, align 4
br label %bb21
bb21: ; preds = %bb2, %bb14
br label %bb22
bb22: ; preds = %bb21
%indvars.iv.next = add nuw nsw i64 %indvars.iv, 1
br label %bb1
bb23: ; preds = %bb1
ret void
}