mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-23 11:13:28 +01:00
c7112b7126
This is https://bugs.llvm.org/show_bug.cgi?id=44257. In LLVM style we always print `0` as addend when dumping SHT_REL relocations. It is confusing, this patch stops printing it as the first comment on the bug page suggests. Differential revision: https://reviews.llvm.org/D93033
41 lines
1.1 KiB
ArmAsm
41 lines
1.1 KiB
ArmAsm
# RUN: llvm-mc -triple=i386-pc-linux-musl %s | FileCheck --check-prefix=PRINT %s
|
|
|
|
# RUN: llvm-mc -filetype=obj -triple=i386-pc-linux-musl %s -o %t
|
|
# RUN: llvm-readobj -r %t | FileCheck %s
|
|
# RUN: llvm-readelf -x .data %t | FileCheck --check-prefix=HEX %s
|
|
|
|
# PRINT: .reloc 2, R_386_NONE, .data
|
|
# PRINT-NEXT: .reloc 1, R_386_NONE, foo+4
|
|
# PRINT-NEXT: .reloc 0, R_386_NONE, 8
|
|
# PRINT-NEXT: .reloc 0, R_386_32, .data+2
|
|
# PRINT-NEXT: .reloc 0, R_386_IRELATIVE, foo+3
|
|
# PRINT-NEXT: .reloc 0, R_386_GOT32X, 5
|
|
|
|
# X86 relocations use the Elf32_Rel format. Addends are neither stored in the
|
|
# relocation entries nor applied in the referenced locations.
|
|
# CHECK: 0x2 R_386_NONE .data
|
|
# CHECK-NEXT: 0x1 R_386_NONE foo
|
|
# CHECK-NEXT: 0x0 R_386_NONE -
|
|
# CHECK-NEXT: 0x0 R_386_32 .data
|
|
# CHECK-NEXT: 0x0 R_386_IRELATIVE foo
|
|
# CHECK-NEXT: 0x0 R_386_GOT32X -
|
|
|
|
# HEX: 0x00000000 00000000 00000000
|
|
|
|
.text
|
|
ret
|
|
nop
|
|
nop
|
|
.reloc 2, R_386_NONE, .data
|
|
.reloc 1, R_386_NONE, foo+4
|
|
.reloc 0, R_386_NONE, 8
|
|
.reloc 0, R_386_32, .data+2
|
|
.reloc 0, R_386_IRELATIVE, foo+3
|
|
.reloc 0, R_386_GOT32X, 5
|
|
|
|
.data
|
|
.globl foo
|
|
foo:
|
|
.long 0
|
|
.long 0
|