mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-24 03:33:20 +01:00
497a3115c3
After recognising that a certain narrow instruction might need a relocation to be represented, we used to unconditionally relax it to a Thumb2 instruction to permit this. Unfortunately, some CPUs (e.g. v6m) don't even have most Thumb2 instructions, so we end up emitting a completely invalid instruction. Theoretically, ELF does have relocations for these situations; but they are fairly unusable with such short ranges and the ABI document even says they're documented "for completeness". So an error is probably better there too. rdar://20391953 llvm-svn: 234195
20 lines
873 B
ArmAsm
20 lines
873 B
ArmAsm
@ RUN: not llvm-mc -triple thumbv6m-none-macho -filetype=obj -o /dev/null %s 2>&1 | FileCheck --check-prefix=CHECK-ERROR %s
|
|
@ RUN: llvm-mc -triple thumbv7m-none-macho -filetype=obj -o %t %s
|
|
@ RUN: llvm-objdump -d -r -triple thumbv7m-none-macho %t | FileCheck --check-prefix=CHECK-MACHO %s
|
|
@ RUN: llvm-mc -triple thumbv7m-none-eabi -filetype=obj -o %t %s
|
|
@ RUN: llvm-objdump -d -r -triple thumbv7m-none-eabi %t | FileCheck --check-prefix=CHECK-ELF %s
|
|
|
|
.global func1
|
|
_func1:
|
|
@ There is no MachO relocation for Thumb1's unconditional branch, so
|
|
@ this is unrepresentable. FIXME: I think ELF could represent this.
|
|
b _func2
|
|
|
|
@ CHECK-ERROR: unsupported relocation on symbol
|
|
|
|
@ CHECK-MACHO: ff f7 fe bf b.w #-4
|
|
@ CHECK-MACHO-NEXT: ARM_THUMB_RELOC_BR22
|
|
|
|
@ CHECK-ELF: ff f7 fe bf b.w #-4
|
|
@ CHECK-ELF-NEXT: R_ARM_THM_JUMP24 _func2
|