9e9907f1cf
Similar to 806761a762.
For IR files without a target triple, -mtriple= specifies the full
target triple while -march= merely sets the architecture part of the
default target triple, leaving a target triple which may not make sense,
e.g. amdgpu-apple-darwin.
Therefore, -march= is error-prone and not recommended for tests without
a target triple. The issue has been benign as we recognize
$unknown-apple-darwin as ELF instead of rejecting it outrightly.
This patch changes AMDGPU tests to not rely on the default
OS/environment components. Tests that need fixes are not changed:
```
LLVM :: CodeGen/AMDGPU/fabs.f64.ll
LLVM :: CodeGen/AMDGPU/fabs.ll
LLVM :: CodeGen/AMDGPU/floor.ll
LLVM :: CodeGen/AMDGPU/fneg-fabs.f64.ll
LLVM :: CodeGen/AMDGPU/fneg-fabs.ll
LLVM :: CodeGen/AMDGPU/r600-infinite-loop-bug-while-reorganizing-vector.ll
LLVM :: CodeGen/AMDGPU/schedule-if-2.ll
```
30 lines
754 B
LLVM
30 lines
754 B
LLVM
; RUN: llc -mtriple=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 amdgpu_kernel void @test(ptr addrspace(1) %out, ptr addrspace(1) %in, i32 %cond) {
|
|
entry:
|
|
%0 = icmp eq i32 %cond, 0
|
|
br i1 %0, label %endif, label %if
|
|
|
|
if:
|
|
%1 = load i32, ptr addrspace(1) %in
|
|
br label %endif
|
|
|
|
endif:
|
|
%x = phi i32 [ %1, %if], [ 0, %entry]
|
|
store i32 %x, ptr addrspace(1) %out
|
|
br label %done
|
|
|
|
done:
|
|
ret void
|
|
}
|