Remove "CHECK: br" from some unit tests
They happen to match %polly.subregion.iv.inc = add i32 %polly.subregion.iv, 1 ^^ ^^ that is, are misleading in what they actually check. llvm-svn: 250408
This commit is contained in:
parent
8008de5551
commit
90428328ee
|
@ -20,7 +20,6 @@ loop:
|
|||
; CHECK-NEXT: store float %p_val0, float* %merge.phiops
|
||||
; CHECK-NEXT: store float %p_val1, float* %val1.s2a
|
||||
; CHECK-NEXT: store float %p_val2, float* %val2.s2a
|
||||
; CHECK-NEXT: br
|
||||
|
||||
; FIXME -> The last two writes are not really needed and can be dropped if the
|
||||
; incoming block of the PHI and the value that is used share the same
|
||||
|
@ -31,14 +30,12 @@ branch1:
|
|||
|
||||
; CHECK-LABEL: polly.stmt.branch1:
|
||||
; CHECK-NEXT: store float %p_val1, float* %merge.phiops
|
||||
; CHECK-NEXT: br
|
||||
|
||||
branch2:
|
||||
br label %backedge
|
||||
|
||||
; CHECK-LABEL: polly.stmt.branch2:
|
||||
; CHECK-NEXT: store float %p_val2, float* %merge.phiops
|
||||
; CHECK-NEXT: br
|
||||
|
||||
backedge:
|
||||
%merge = phi float [%val0, %loop], [%val1, %branch1], [%val2, %branch2]
|
||||
|
|
|
@ -17,7 +17,6 @@ loop:
|
|||
; CHECK-NEXT: %p_val1 = fadd float 1.000000e+00, 2.000000e+00
|
||||
; CHECK-NEXT: store float %p_val0, float* %merge.phiops
|
||||
; CHECK-NEXT: store float %p_val1, float* %val1.s2a
|
||||
; CHECK-NEXT: br
|
||||
|
||||
; The interesting instruction here is %val2, which does not dominate the exit of
|
||||
; the non-affine region. Care needs to be taken when code-generating this write.
|
||||
|
@ -43,7 +42,6 @@ branch2:
|
|||
|
||||
; CHECK-LABEL: polly.stmt.branch2:
|
||||
; CHECK-NEXT: store float %p_val2, float* %merge.phiops
|
||||
; CHECK-NEXT: br
|
||||
|
||||
backedge:
|
||||
%merge = phi float [%val0, %loop], [%val1, %branch1], [%val2, %branch2]
|
||||
|
|
Loading…
Reference in New Issue