252c42354e
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.
23 lines
826 B
ArmAsm
23 lines
826 B
ArmAsm
! RUN: not llvm-mc %s -triple=sparc -show-encoding 2>&1 | FileCheck %s --check-prefix=CHECK --check-prefix=V8
|
|
! RUN: not llvm-mc %s -triple=sparcv9 -show-encoding 2>&1 | FileCheck %s --check-prefix=CHECK --check-prefix=V9
|
|
|
|
! Test the lower and upper bounds of 'set'
|
|
! CHECK: argument must be between
|
|
set -2147483649, %o1
|
|
! CHECK: argument must be between
|
|
set 4294967296, %o1
|
|
|
|
! V8: unexpected token
|
|
! V9: unknown membar tag
|
|
membar #BadTag
|
|
|
|
! V8: instruction requires a CPU feature not currently enabled
|
|
! V9: invalid membar mask number
|
|
membar -127
|
|
|
|
! Test the boundary checks on the shift amount
|
|
! V8: immediate shift value out of range
|
|
sll %g1, 32, %g2
|
|
! V9: immediate shift value out of range
|
|
slx %g1, 64, %g2
|