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
```
17 lines
577 B
LLVM
17 lines
577 B
LLVM
; RUN: llc -mtriple=amdgcn -mcpu=tahiti -mattr=-promote-alloca -verify-machineinstrs < %s
|
|
; RUN: llc -mtriple=amdgcn -mcpu=tonga -mattr=-promote-alloca -verify-machineinstrs < %s
|
|
|
|
; Test that INSERT_SUBREG instructions don't have non-register operands after
|
|
; instruction selection.
|
|
|
|
; Make sure this doesn't crash
|
|
; CHECK-LABEL: test:
|
|
define amdgpu_kernel void @test(ptr addrspace(1) %out) {
|
|
entry:
|
|
%tmp0 = alloca [16 x i32], addrspace(5)
|
|
%tmp1 = ptrtoint ptr addrspace(5) %tmp0 to i32
|
|
%tmp2 = sext i32 %tmp1 to i64
|
|
store i64 %tmp2, ptr addrspace(1) %out
|
|
ret void
|
|
}
|