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
```
16 lines
585 B
LLVM
16 lines
585 B
LLVM
; RUN: llc -mtriple=amdgcn -verify-machineinstrs < %s | FileCheck -check-prefix=SI %s
|
|
; RUN: llc -mtriple=amdgcn -mcpu=tonga -verify-machineinstrs < %s | FileCheck -check-prefix=SI %s
|
|
|
|
; Make sure the GlobalDirective isn't merged with the function name
|
|
|
|
; SI: .globl foo
|
|
; SI: {{^}}foo:
|
|
define amdgpu_kernel void @foo(ptr addrspace(1) %out, ptr addrspace(1) %in) {
|
|
%b_ptr = getelementptr i32, ptr addrspace(1) %in, i32 1
|
|
%a = load i32, ptr addrspace(1) %in
|
|
%b = load i32, ptr addrspace(1) %b_ptr
|
|
%result = add i32 %a, %b
|
|
store i32 %result, ptr addrspace(1) %out
|
|
ret void
|
|
}
|