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
1007 B
YAML
29 lines
1007 B
YAML
# RUN: llc -mtriple=amdgcn -mcpu=gfx90a -run-pass=machine-cp -verify-machineinstrs -o - %s | FileCheck --check-prefix=GCN %s
|
|
|
|
# GCN-LABEL: name: mcp_aligned_vgprs
|
|
# GCN: $vgpr0_vgpr1 = V_PK_MUL_F32 0, $sgpr0_sgpr1
|
|
# GCN: $vgpr3_vgpr4 = COPY killed renamable $vgpr0_vgpr1
|
|
---
|
|
name: mcp_aligned_vgprs
|
|
body: |
|
|
bb.0.entry:
|
|
|
|
renamable $vgpr0_vgpr1 = V_PK_MUL_F32 0, $sgpr0_sgpr1, 0, 0, 0, 0, 0, 0, 0, implicit $mode, implicit $exec
|
|
renamable $vgpr3_vgpr4 = COPY killed renamable $vgpr0_vgpr1
|
|
S_ENDPGM 0, implicit $vgpr3_vgpr4
|
|
...
|
|
|
|
# GCN-LABEL: name: mcp_aligned_agprs
|
|
# GCN: $agpr0_agpr1 = GLOBAL_LOAD_DWORDX2_SADDR $sgpr0_sgpr1, $vgpr10
|
|
# GCN: $agpr3_agpr4 = COPY killed renamable $agpr0_agpr1
|
|
---
|
|
name: mcp_aligned_agprs
|
|
body: |
|
|
bb.0.entry:
|
|
|
|
renamable $agpr0_agpr1 = GLOBAL_LOAD_DWORDX2_SADDR $sgpr0_sgpr1, $vgpr10, 0, 0, implicit $exec
|
|
renamable $agpr3_agpr4 = COPY killed renamable $agpr0_agpr1
|
|
S_ENDPGM 0, implicit $agpr3_agpr4
|
|
|
|
...
|