9e9907f1cf
Similar to 806761a7629df268c8aed49657aeccffa6bca449. 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 ```
23 lines
984 B
YAML
23 lines
984 B
YAML
# NOTE: Assertions have been autogenerated by utils/update_mir_test_checks.py
|
|
# RUN: llc -o - %s -mtriple=amdgcn -mcpu=gfx1010 -run-pass=machine-cp -verify-machineinstrs | FileCheck %s
|
|
|
|
---
|
|
name: undef_copy_propagation
|
|
tracksRegLiveness: true
|
|
body: |
|
|
bb.0:
|
|
|
|
; CHECK-LABEL: name: undef_copy_propagation
|
|
; CHECK: renamable $vgpr0 = COPY undef renamable $sgpr42, implicit $exec
|
|
; CHECK-NEXT: renamable $vgpr1 = COPY undef $sgpr42
|
|
; CHECK-NEXT: renamable $vgpr2 = COPY undef $sgpr42
|
|
; CHECK-NEXT: renamable $vgpr3 = COPY undef $sgpr42
|
|
; CHECK-NEXT: EXP_DONE 0, killed $vgpr0, killed $vgpr1, killed $vgpr2, killed $vgpr3, -1, -1, 15, implicit $exec
|
|
renamable $vgpr0 = COPY undef renamable $sgpr42, implicit $exec
|
|
renamable $vgpr1 = COPY renamable $vgpr0
|
|
renamable $vgpr2 = COPY renamable $vgpr0
|
|
renamable $vgpr3 = COPY renamable $vgpr0
|
|
|
|
EXP_DONE 0, killed $vgpr0, killed $vgpr1, killed $vgpr2, killed $vgpr3, -1, -1, 15, implicit $exec
|
|
...
|