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
```
13 lines
632 B
LLVM
13 lines
632 B
LLVM
; RUN: llc -mtriple=amdgcn -mcpu=tahiti -verify-machineinstrs< %s
|
|
; RUN: llc -mtriple=amdgcn -mcpu=tonga -verify-machineinstrs< %s
|
|
|
|
; This tests for a bug that caused a crash in
|
|
; AMDGPUDAGToDAGISel::SelectMUBUFScratch() which is used for selecting
|
|
; scratch loads and stores.
|
|
; CHECK-LABEL: {{^}}store_vector_ptrs:
|
|
define amdgpu_kernel void @store_vector_ptrs(ptr addrspace(5) %out, <4 x ptr addrspace(5)> %array) nounwind {
|
|
%p = getelementptr [1024 x i32], <4 x ptr addrspace(5)> %array, <4 x i16> zeroinitializer, <4 x i16> <i16 16, i16 16, i16 16, i16 16>
|
|
store <4 x ptr addrspace(5)> %p, ptr addrspace(5) %out
|
|
ret void
|
|
}
|