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/escaping_empty_scop.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

59 lines
1.6 KiB
LLVM
Raw Normal View History

[ScopBuilder] Make -polly-stmt-granularity=scalar-indep the default. Splitting basic blocks into multiple statements if there are now additional scalar dependencies gives more freedom to the scheduler, but more statements also means higher compile-time complexity. Switch to finer statement granularity, the additional compile time should be limited by the number of operations quota. The regression tests are written for the -polly-stmt-granularity=bb setting, therefore we add that flag to those tests that break with the new default. Some of the tests only fail because the statements are named differently due to a basic block resulting in multiple statements, but which are removed during simplification of statements without side-effects. Previous commits tried to reduce this effect, but it is not completely avoidable. Differential Revision: https://reviews.llvm.org/D42151 llvm-svn: 324169
2018-02-03 14:59:47 +08:00
; RUN: opt %loadPolly -polly-stmt-granularity=bb -polly-scops -analyze < %s | FileCheck %s
Model scalar writes with uses outside the SCoP These write are important as they will force the scheduling and code generation of an otherwise trivial statement and also impose an order of execution needed to guarantee the correct final value for a scalar in a loop. Added test case modeled after ClamAV/clamscan. llvm-svn: 228847
2015-02-12 01:02:52 +08:00
;
; void g();
; int f(int *A) {
; int a0 = 0, a1 = 0, a2 = 0;
; for (int i = 0; i < 1000; i++) {
; a0 = 2 * i;
; // split
; A[0] = i;
; a1 = 2 * i;
; // split
; a2 = 2 * i;
; }
; g();
; return a1 + a2;
; }
;
; CHECK: Stmt_bb1
; CHECK: MustWriteAccess := [Reduction Type: NONE] [Scalar: 1]
; CHECK: { Stmt_bb1[i0] -> MemRef_a_0[] };
; CHECK: Stmt_bb2
; CHECK: MustWriteAccess := [Reduction Type: NONE] [Scalar: 1]
; CHECK: { Stmt_bb2[i0] -> MemRef_a_1[] };
; CHECK: Stmt_bb3
; CHECK: MustWriteAccess := [Reduction Type: NONE] [Scalar: 1]
; CHECK: { Stmt_bb3[i0] -> MemRef_a_2[] };
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
define i32 @f(i32* %A) {
bb:
br label %bb1
bb1: ; preds = %bb3, %bb
%i.0 = phi i32 [ 0, %bb ], [ %tmp4, %bb3 ]
%a.0 = mul i32 %i.0, 2
br label %bb2
bb2: ; preds = %bb1
%a.1 = mul i32 %i.0, 2
store i32 %i.0, i32 *%A, align 4
br label %bb3
bb3: ; preds = %bb2
%tmp = shl nsw i32 %i.0, 1
%tmp4 = add nuw nsw i32 %i.0, 1
%a.2 = mul i32 %i.0, 2
%exitcond = icmp ne i32 %i.0, 1000
br i1 %exitcond, label %bb1, label %bb5
bb5: ; preds = %bb1
[opaque pointer types] Explicit non-pointer type for call expressions (migration for recent LLVM change to textual IR for calls) llvm-svn: 235146
2015-04-17 07:24:52 +08:00
call void (...) @g() #2
Model scalar writes with uses outside the SCoP These write are important as they will force the scheduling and code generation of an otherwise trivial statement and also impose an order of execution needed to guarantee the correct final value for a scalar in a loop. Added test case modeled after ClamAV/clamscan. llvm-svn: 228847
2015-02-12 01:02:52 +08:00
%add = add i32 %a.0, %a.1
%add2 = add i32 %add, %a.2
ret i32 %add2
}
declare void @g(...) #1