R600: Correctly handle vertex fetch clauses the precede ENDIFs

The control flow finalizer would sometimes use an ALU_POP_AFTER
instruction before the vetex fetch clause instead of using a POP
instruction after it.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@199917 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Tom Stellard 2014-01-23 18:49:31 +00:00
parent 01df2fa3c4
commit cbf79028c3
2 changed files with 30 additions and 0 deletions

View File

@ -501,6 +501,7 @@ public:
DEBUG(dbgs() << CfCount << ":"; I->dump(););
FetchClauses.push_back(MakeFetchClause(MBB, I));
CfCount++;
LastAlu.back() = 0;
continue;
}

View File

@ -0,0 +1,29 @@
; RUN: llc -march=r600 -mcpu=redwood %s -o - | FileCheck %s
; This tests for a bug where vertex fetch clauses right before an ENDIF
; instruction where being emitted after the ENDIF. We were using ALU_POP_AFTER
; for the ALU clause before the vetex fetch instead of emitting a POP instruction
; after the fetch clause.
; CHECK-LABEL: @test
; CHECK-NOT: ALU_POP_AFTER
; CHECK: TEX
; CHECK-NEXT: POP
define void @test(i32 addrspace(1)* %out, i32 addrspace(1)* %in, i32 %cond) {
entry:
%0 = icmp eq i32 %cond, 0
br i1 %0, label %endif, label %if
if:
%1 = load i32 addrspace(1)* %in
br label %endif
endif:
%x = phi i32 [ %1, %if], [ 0, %entry]
store i32 %x, i32 addrspace(1)* %out
br label %done
done:
ret void
}