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
```
25 lines
825 B
YAML
25 lines
825 B
YAML
# RUN: llc -mcpu=gfx900 -mtriple=amdgcn -verify-machineinstrs -run-pass post-RA-hazard-rec %s -o - | FileCheck %s
|
|
|
|
# If an INLINEASM statement is preceded by a vmem store of more than 8 bytes *and*
|
|
# the INLINEASM defs the vregs holding the data-to-be-stored by that preceding store,
|
|
# then the hazard recognizer should insert a s_nop in between them.
|
|
|
|
...
|
|
|
|
# CHECK-LABEL: name: hazard-inlineasm
|
|
# CHECK: FLAT_STORE_DWORDX4
|
|
# CHECK-NEXT: S_NOP 0
|
|
# CHECK-NEXT: INLINEASM
|
|
|
|
---
|
|
name: hazard-inlineasm
|
|
|
|
body: |
|
|
bb.0:
|
|
FLAT_STORE_DWORDX4 $vgpr49_vgpr50, $vgpr26_vgpr27_vgpr28_vgpr29, 0, 0, implicit $exec, implicit $flat_scr
|
|
INLINEASM &"v_mad_u64_u32 $0, $1, $2, $3, $4", 0, 2621450, def $vgpr26_vgpr27, 2818058, def dead $sgpr14_sgpr15, 589833, $sgpr12, 327689, killed $vgpr51, 2621449, $vgpr46_vgpr47
|
|
S_ENDPGM 0
|
|
...
|
|
|
|
|