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
```
16 lines
475 B
LLVM
16 lines
475 B
LLVM
; RUN: llc -mtriple=r600 -mcpu=cypress < %s | FileCheck %s
|
|
|
|
; CHECK-LABEL: {{^}}kernel_arg_i64:
|
|
define amdgpu_kernel void @kernel_arg_i64(ptr addrspace(1) %out, i64 %a) nounwind {
|
|
store i64 %a, ptr addrspace(1) %out, align 8
|
|
ret void
|
|
}
|
|
|
|
; i64 arg works, v1i64 arg does not.
|
|
; CHECK-LABEL: {{^}}kernel_arg_v1i64:
|
|
define amdgpu_kernel void @kernel_arg_v1i64(ptr addrspace(1) %out, <1 x i64> %a) nounwind {
|
|
store <1 x i64> %a, ptr addrspace(1) %out, align 8
|
|
ret void
|
|
}
|
|
|