2208c97c1b
Similar to 806761a7629df268c8aed49657aeccffa6bca449 -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. 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.
27 lines
1008 B
LLVM
27 lines
1008 B
LLVM
; RUN: llc -mtriple=hexagon -filetype=obj < %s | llvm-objdump -d - | FileCheck %s
|
|
|
|
; The output assembly (textual) contains the instruction
|
|
; r29 = add(r29,#4294967136)
|
|
; The value 4294967136 is -160 when interpreted as a signed 32-bit
|
|
; integer, so it fits in the range of the immediate operand without
|
|
; a constant extender. The range check in HexagonInstrInfo was putting
|
|
; the operand value into an int variable, reporting no need for an
|
|
; extender. This resulted in a packet with 4 instructions, including
|
|
; the "add". The corresponding check in HexagonMCInstrInfo was using
|
|
; an int64_t variable, causing an extender to be emitted when lowering
|
|
; to MCInst, and resulting in a packet with 5 instructions.
|
|
|
|
; Check that this doesn't crash.
|
|
; CHECK: r29 = add(r29,#-0xa0)
|
|
|
|
target triple = "hexagon-unknown-linux-gnu"
|
|
|
|
define float @f0() {
|
|
b0:
|
|
%v0 = alloca i8, i32 0, align 1
|
|
%v1 = alloca float, i32 -42, align 4
|
|
%v2 = load float, ptr %v1, align 4
|
|
store i8 0, ptr %v0, align 1
|
|
ret float %v2
|
|
}
|