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 ```
15 lines
424 B
YAML
15 lines
424 B
YAML
# RUN: llc -mtriple=amdgcn -run-pass si-fold-operands -verify-machineinstrs -o - %s | FileCheck %s
|
|
---
|
|
# Make sure there is no crash when trying to fold an immediate into an
|
|
# implicit use
|
|
|
|
# CHECK: %0:vgpr_32 = V_MOV_B32_e32 0, implicit $exec
|
|
# CHECK-NEXT: S_ENDPGM 0, implicit %0
|
|
name: fold_imm_implicit_operand
|
|
body: |
|
|
bb.0:
|
|
%0:vgpr_32 = V_MOV_B32_e32 0, implicit $exec
|
|
S_ENDPGM 0, implicit %0
|
|
|
|
...
|