
The issue is uncovered by #47698: for assembly files, -triple= specifies the full target triple while -arch= merely sets the architecture part of the default target triple, leaving a target triple which may not make sense, e.g. riscv64-apple-darwin. Therefore, -arch= is error-prone and not recommended for tests. The issue has been benign as we recognize $unknown-apple-darwin as ELF instead of rejecting it outrightly. Due to the nature of the issue, we don't see the issue in tests using architectures that any of Mach-O/COFF/XCOFF supports.
12 lines
574 B
ArmAsm
12 lines
574 B
ArmAsm
! RUN: llvm-mc %s -triple=sparc -mcpu=leon3 -show-encoding | FileCheck %s
|
|
! RUN: llvm-mc %s -triple=sparc -mcpu=ut699 -show-encoding | FileCheck %s
|
|
! RUN: llvm-mc %s -triple=sparc -mcpu=gr712rc -show-encoding | FileCheck %s
|
|
! RUN: llvm-mc %s -triple=sparc -mcpu=leon4 -show-encoding | FileCheck %s
|
|
! RUN: llvm-mc %s -triple=sparc -mcpu=gr740 -show-encoding | FileCheck %s
|
|
|
|
! CHECK: umac %i0, %l6, %o2 ! encoding: [0x95,0xf6,0x00,0x16]
|
|
umac %i0, %l6, %o2
|
|
|
|
! CHECK: smac %i0, %l6, %o2 ! encoding: [0x95,0xfe,0x00,0x16]
|
|
smac %i0, %l6, %o2
|