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
```
19 lines
637 B
LLVM
19 lines
637 B
LLVM
; RUN: not --crash llc -mtriple=amdgcn -mcpu=tahiti -verify-machineinstrs -o /dev/null %s 2>&1 | FileCheck %s
|
|
|
|
; FIXME: It should be invalid IR to have a call to a kernel, but this
|
|
; is currently relied on, but should be eliminated before codegen.
|
|
define amdgpu_kernel void @callee_kernel(ptr addrspace(1) %out) #0 {
|
|
entry:
|
|
store volatile i32 0, ptr addrspace(1) %out
|
|
ret void
|
|
}
|
|
|
|
; CHECK: LLVM ERROR: Unsupported calling convention for call
|
|
define amdgpu_kernel void @caller_kernel(ptr addrspace(1) %out) #0 {
|
|
entry:
|
|
call amdgpu_kernel void @callee_kernel(ptr addrspace(1) %out)
|
|
ret void
|
|
}
|
|
|
|
attributes #0 = { nounwind noinline }
|