
The issue is uncovered by #47698: for IR files without a target triple, -mtriple= specifies the full target triple while -march= 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, -march= is error-prone and not recommended for tests without a target triple. The issue has been benign as we recognize $unknown-apple-darwin as ELF instead of rejecting it outrightly.
13 lines
337 B
LLVM
13 lines
337 B
LLVM
; RUN: llc -mtriple=hexagon -O0 %s -o - | llvm-mc -triple=hexagon -filetype=obj | llvm-objdump --no-print-imm-hex -d - | FileCheck %s
|
|
|
|
; CHECK: immext(#16777216)
|
|
; CHECK-NEXT: r0 = add(r0,##16777279)
|
|
|
|
define void @f0(i32 %a0) {
|
|
b0:
|
|
%v0 = add i32 16777279, %a0
|
|
%v1 = alloca i32, align 4
|
|
store i32 %v0, ptr %v1, align 4
|
|
ret void
|
|
}
|