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
```
29 lines
1020 B
LLVM
29 lines
1020 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
|
|
; RUN: llc -mtriple=amdgcn -mcpu=gfx900 -verify-machineinstrs < %s | FileCheck -check-prefix=GCN %s
|
|
; RUN: llc -global-isel -mtriple=amdgcn -mcpu=gfx900 -verify-machineinstrs < %s | FileCheck -check-prefix=GCN %s
|
|
|
|
define amdgpu_kernel void @test_s_sethalt() {
|
|
; GCN-LABEL: test_s_sethalt:
|
|
; GCN: ; %bb.0:
|
|
; GCN-NEXT: s_sethalt 0
|
|
; GCN-NEXT: s_sethalt 1
|
|
; GCN-NEXT: s_sethalt 2
|
|
; GCN-NEXT: s_sethalt 3
|
|
; GCN-NEXT: s_sethalt 4
|
|
; GCN-NEXT: s_sethalt 5
|
|
; GCN-NEXT: s_sethalt 6
|
|
; GCN-NEXT: s_sethalt 7
|
|
; GCN-NEXT: s_endpgm
|
|
call void @llvm.amdgcn.s.sethalt(i32 0)
|
|
call void @llvm.amdgcn.s.sethalt(i32 1)
|
|
call void @llvm.amdgcn.s.sethalt(i32 2)
|
|
call void @llvm.amdgcn.s.sethalt(i32 3)
|
|
call void @llvm.amdgcn.s.sethalt(i32 4)
|
|
call void @llvm.amdgcn.s.sethalt(i32 5)
|
|
call void @llvm.amdgcn.s.sethalt(i32 6)
|
|
call void @llvm.amdgcn.s.sethalt(i32 7)
|
|
ret void
|
|
}
|
|
|
|
declare void @llvm.amdgcn.s.sethalt(i32)
|