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.
75 lines
1.1 KiB
ArmAsm
75 lines
1.1 KiB
ArmAsm
// RUN: llvm-mc -triple=amdgcn -mcpu=gfx1010 -show-encoding %s | FileCheck %s --check-prefix=GFX10
|
|
// RUN: llvm-mc -triple=amdgcn -mcpu=gfx1010 -filetype=obj %s | llvm-objdump -d --mcpu=gfx1010 - | FileCheck %s --check-prefix=BIN
|
|
s_getpc_b64 s[0:1]
|
|
s_cbranch_vccnz BB0_1
|
|
// GFX10: s_cbranch_vccnz BB0_1 ; encoding: [A,A,0x87,0xbf]
|
|
// GFX10-NEXT: ; fixup A - offset: 0, value: BB0_1, kind: fixup_si_sopp_br
|
|
// BIN: s_cbranch_vccnz BB0_1 // 000000000004: BF870040
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
s_nop 0
|
|
BB0_1:
|
|
s_nop 0
|
|
s_endpgm
|