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/phi-defined-before-scop.ll

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

53 lines
2.0 KiB
LLVM
Raw Normal View History

Add a missing '-S' llvm-svn: 251199
2015-10-25 03:02:01 +08:00
; RUN: opt %loadPolly -polly-codegen -S < %s | FileCheck %s
BlockGenerator: Do not assert when finding model PHI nodes defined outside the scop Such PHI nodes can not only appear in the ExitBlock of the Scop, but indeed any scalar PHI node above the scop and used in the scop is modeled as scalar read access. llvm-svn: 251198
2015-10-25 03:01:09 +08:00
; CHECK-LABEL: polly.merge_new_and_old:
executeScopConditionally: Introduce special exiting block When introducing separate control flow for the original and optimized code we introduce now a special 'ExitingBlock': \ / EnteringBB | SplitBlock---------\ _____|_____ | / EntryBB \ StartBlock | (region) | | \_ExitingBB_/ ExitingBlock | | MergeBlock---------/ | ExitBB / \ This 'ExitingBlock' contains code such as the final_reloads for scalars, which previously were just added to whichever statement/loop_exit/branch-merge block had been generated last. Having an explicit basic block makes it easier to find these constructs when looking at the CFG. llvm-svn: 255107
2015-12-09 19:38:22 +08:00
; CHECK-NEXT: %tmp7.ph.merge = phi %struct.wibble* [ %tmp7.ph.final_reload, %polly.exiting ], [ %tmp7.ph, %bb6.region_exiting ]
BlockGenerator: Do not assert when finding model PHI nodes defined outside the scop Such PHI nodes can not only appear in the ExitBlock of the Scop, but indeed any scalar PHI node above the scop and used in the scop is modeled as scalar read access. llvm-svn: 251198
2015-10-25 03:01:09 +08:00
; CHECK-LABEL: polly.stmt.bb3:
ScopInfo: Never add read accesses for synthesizable values Before adding a MK_Value READ MemoryAccess, check whether the read is necessary or synthesizable. Synthesizable values are later generated by the SCEVExpander and therefore do not need to be transferred explicitly. This can happen because the check for synthesizability has presumbly been forgotten in the case where a phi's incoming value has been defined in a different statement. Differential Revision: http://reviews.llvm.org/D15687 llvm-svn: 258998
2016-01-28 06:51:56 +08:00
; CHECK-NEXT: store %struct.wibble* %tmp2, %struct.wibble** %tmp7.s2a
BlockGenerator: Do not assert when finding model PHI nodes defined outside the scop Such PHI nodes can not only appear in the ExitBlock of the Scop, but indeed any scalar PHI node above the scop and used in the scop is modeled as scalar read access. llvm-svn: 251198
2015-10-25 03:01:09 +08:00
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
%struct.blam = type { i32, i32, i32, i32, i32, i32, i32, i32, i32, i32 }
%struct.wibble = type { i32, %struct.wibble*, %struct.wibble* }
@global = external global %struct.blam*, align 8
; Function Attrs: nounwind uwtable
define void @wobble() #0 {
bb:
br label %bb1
bb1: ; preds = %bb6, %bb
%tmp2 = phi %struct.wibble* [ %tmp7, %bb6 ], [ undef, %bb ]
%tmp = load %struct.blam*, %struct.blam** @global, align 8, !tbaa !1
br label %bb3
bb3: ; preds = %bb1
%tmp4 = getelementptr inbounds %struct.blam, %struct.blam* %tmp, i64 0, i32 1
br i1 false, label %bb6, label %bb5
bb5: ; preds = %bb3
br label %bb6
bb6: ; preds = %bb5, %bb3
%tmp7 = phi %struct.wibble* [ %tmp2, %bb3 ], [ undef, %bb5 ]
br i1 undef, label %bb8, label %bb1
bb8: ; preds = %bb6
br label %bb9
bb9: ; preds = %bb8
unreachable
}
Migrate function attribute "no-frame-pointer-elim"="false" to "frame-pointer"="none" as cleanups after D56351
2019-12-25 08:11:33 +08:00
attributes #0 = { nounwind uwtable "disable-tail-calls"="false" "less-precise-fpmad"="false" "frame-pointer"="none" "no-infs-fp-math"="false" "no-nans-fp-math"="false" "stack-protector-buffer-size"="8" "target-cpu"="x86-64" "target-features"="+mmx,+sse,+sse2" "unsafe-fp-math"="false" "use-soft-float"="false" }
BlockGenerator: Do not assert when finding model PHI nodes defined outside the scop Such PHI nodes can not only appear in the ExitBlock of the Scop, but indeed any scalar PHI node above the scop and used in the scop is modeled as scalar read access. llvm-svn: 251198
2015-10-25 03:01:09 +08:00
!llvm.ident = !{!0}
!0 = !{!"clang version 3.8.0 (trunk 250010) (llvm/trunk 250018)"}
!1 = !{!2, !2, i64 0}
!2 = !{!"any pointer", !3, i64 0}
!3 = !{!"omnipotent char", !4, i64 0}
!4 = !{!"Simple C/C++ TBAA"}