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.
21 lines
694 B
ArmAsm
21 lines
694 B
ArmAsm
# RUN: llvm-mc %s -triple=mips -mcpu=mips32 | \
|
|
# RUN: FileCheck %s -check-prefix=CHECK-ASM
|
|
#
|
|
# RUN: llvm-mc %s -triple=mips -mcpu=mips32 -filetype=obj -o - | \
|
|
# RUN: llvm-readobj -A - | \
|
|
# RUN: FileCheck %s -check-prefix=CHECK-OBJ
|
|
|
|
# CHECK-ASM: .module softfloat
|
|
|
|
# Check if the MIPS.abiflags section was correctly emitted:
|
|
# CHECK-OBJ: MIPS ABI Flags {
|
|
# CHECK-OBJ: FP ABI: Soft float (0x3)
|
|
# CHECK-OBJ: CPR1 size: 0
|
|
# CHECK-OBJ: }
|
|
|
|
.module softfloat
|
|
|
|
# FIXME: Test should include gnu_attributes directive when implemented.
|
|
# An explicit .gnu_attribute must be checked against the effective
|
|
# command line options and any inconsistencies reported via a warning.
|