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.
17 lines
524 B
ArmAsm
17 lines
524 B
ArmAsm
# RUN: llvm-mc < %s -triple=mips -mcpu=mips32r2 -filetype=obj -o - | \
|
|
# RUN: llvm-readobj -A - | FileCheck --check-prefix=CHECK-OBJ %s
|
|
# RUN: llvm-mc < %s -triple=mips -mcpu=mips32r2 -filetype=asm -o - | \
|
|
# RUN: FileCheck --check-prefix=CHECK-ASM %s
|
|
|
|
# Test that the .module directive sets the MT flag in .MIPS.abiflags when
|
|
# assembling to boject files.
|
|
|
|
# Test that the .moodule directive is re-emitted when expanding assembly.
|
|
|
|
# CHECK-OBJ: ASEs
|
|
# CHECK-OBJ-NEXT: MT (0x40)
|
|
|
|
# CHECK-ASM: .module mt
|
|
.module mt
|
|
nop
|