maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lld/test/ELF/mips-64-rels.s

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

48 lines
1.8 KiB
ArmAsm
Raw Normal View History

[ELF] Move `# REQUIRES:` line to the top llvm-svn: 335625
2018-06-27 00:58:19 +08:00
# REQUIRES: mips
[ELF][MIPS] Handling 'packed' N64 ABI relocations MIPS N64 ABI packs multiple relocations into the single relocation record. In general, all up to three relocations can have arbitrary types. In fact, Clang and GCC uses only a few combinations. For now, we support two of them. That is allow to pass at least all LLVM test suite cases. <any relocation> / R_MIPS_SUB / R_MIPS_HI16 | R_MIPS_LO16 <any relocation> / R_MIPS_64 / R_MIPS_NONE The first relocation is a 'real' relocation which is calculated using the corresponding symbol's value. The second and the third relocations used to modify result of the first one: extend it to 64-bit, extract high or low part etc. For details, see part 2.9 'Relocation' at https://dmz-portal.mips.com/mw/images/8/82/007-4658-001.pdf llvm-svn: 268876
2016-05-08 22:08:40 +08:00
# Check handling multiple MIPS N64 ABI relocations packed
# into the single relocation record.
# RUN: llvm-mc -filetype=obj -triple=mips64-unknown-linux %s -o %t.o
[mips] Make another set of test cases more tolerant to exact symbol addresses. NFC llvm-svn: 371174
2019-09-06 15:23:02 +08:00
# RUN: echo "SECTIONS { \
# RUN: . = 0x20000; .text ALIGN(0x1000) : { *(.text) } \
# RUN: . = 0x30000; .got : { *(.got) } \
# RUN: }" > %t.script
# RUN: ld.lld %t.o --script %t.script -o %t.exe
# RUN: llvm-objdump -d -s -t --print-imm-hex --no-show-raw-insn %t.exe | FileCheck %s
[ELF][MIPS] Handling 'packed' N64 ABI relocations MIPS N64 ABI packs multiple relocations into the single relocation record. In general, all up to three relocations can have arbitrary types. In fact, Clang and GCC uses only a few combinations. For now, we support two of them. That is allow to pass at least all LLVM test suite cases. <any relocation> / R_MIPS_SUB / R_MIPS_HI16 | R_MIPS_LO16 <any relocation> / R_MIPS_64 / R_MIPS_NONE The first relocation is a 'real' relocation which is calculated using the corresponding symbol's value. The second and the third relocations used to modify result of the first one: extend it to 64-bit, extract high or low part etc. For details, see part 2.9 'Relocation' at https://dmz-portal.mips.com/mw/images/8/82/007-4658-001.pdf llvm-svn: 268876
2016-05-08 22:08:40 +08:00
# RUN: llvm-readobj -r %t.exe | FileCheck -check-prefix=REL %s
# CHECK: __start:
[mips] Make another set of test cases more tolerant to exact symbol addresses. NFC llvm-svn: 371174
2019-09-06 15:23:02 +08:00
# CHECK-NEXT: 21000: lui $gp, 0x1
# ^-- 0x21000 - 0x37ff0
# ^-- 0 - 0xffffffffffff9010
# ^-- %hi(0x16ff0)
[ELF][MIPS] Handling 'packed' N64 ABI relocations MIPS N64 ABI packs multiple relocations into the single relocation record. In general, all up to three relocations can have arbitrary types. In fact, Clang and GCC uses only a few combinations. For now, we support two of them. That is allow to pass at least all LLVM test suite cases. <any relocation> / R_MIPS_SUB / R_MIPS_HI16 | R_MIPS_LO16 <any relocation> / R_MIPS_64 / R_MIPS_NONE The first relocation is a 'real' relocation which is calculated using the corresponding symbol's value. The second and the third relocations used to modify result of the first one: extend it to 64-bit, extract high or low part etc. For details, see part 2.9 'Relocation' at https://dmz-portal.mips.com/mw/images/8/82/007-4658-001.pdf llvm-svn: 268876
2016-05-08 22:08:40 +08:00
# CHECK: loc:
[mips] Make another set of test cases more tolerant to exact symbol addresses. NFC llvm-svn: 371174
2019-09-06 15:23:02 +08:00
# CHECK-NEXT: 21004: daddiu $gp, $gp, 0x6ff0
# ^-- 0x21000 - 0x37ff0
# ^-- 0 - 0xfffffffffffe9010
# ^-- %lo(0x16ff0)
[ELF][MIPS] Handling 'packed' N64 ABI relocations MIPS N64 ABI packs multiple relocations into the single relocation record. In general, all up to three relocations can have arbitrary types. In fact, Clang and GCC uses only a few combinations. For now, we support two of them. That is allow to pass at least all LLVM test suite cases. <any relocation> / R_MIPS_SUB / R_MIPS_HI16 | R_MIPS_LO16 <any relocation> / R_MIPS_64 / R_MIPS_NONE The first relocation is a 'real' relocation which is calculated using the corresponding symbol's value. The second and the third relocations used to modify result of the first one: extend it to 64-bit, extract high or low part etc. For details, see part 2.9 'Relocation' at https://dmz-portal.mips.com/mw/images/8/82/007-4658-001.pdf llvm-svn: 268876
2016-05-08 22:08:40 +08:00
# CHECK: Contents of section .rodata:
[mips] Make another set of test cases more tolerant to exact symbol addresses. NFC llvm-svn: 371174
2019-09-06 15:23:02 +08:00
# CHECK-NEXT: {{[0-9a-f]+}} ffffffff fffe9014
# ^-- 0x21004 - 0x37ff0 = 0xfffffffffffe9014
[ELF][MIPS] Handling 'packed' N64 ABI relocations MIPS N64 ABI packs multiple relocations into the single relocation record. In general, all up to three relocations can have arbitrary types. In fact, Clang and GCC uses only a few combinations. For now, we support two of them. That is allow to pass at least all LLVM test suite cases. <any relocation> / R_MIPS_SUB / R_MIPS_HI16 | R_MIPS_LO16 <any relocation> / R_MIPS_64 / R_MIPS_NONE The first relocation is a 'real' relocation which is calculated using the corresponding symbol's value. The second and the third relocations used to modify result of the first one: extend it to 64-bit, extract high or low part etc. For details, see part 2.9 'Relocation' at https://dmz-portal.mips.com/mw/images/8/82/007-4658-001.pdf llvm-svn: 268876
2016-05-08 22:08:40 +08:00
Don't make _gp absolute. _gp points to a position in the file, so it is not really absolute. It is also simpler to not force it to be absolute, so if there is no strong ABI requirement we should not do it. llvm-svn: 313333
2017-09-15 09:49:01 +08:00
# CHECK: 0000000000037ff0 .got 00000000 .hidden _gp
[ELF][MIPS] Handling 'packed' N64 ABI relocations MIPS N64 ABI packs multiple relocations into the single relocation record. In general, all up to three relocations can have arbitrary types. In fact, Clang and GCC uses only a few combinations. For now, we support two of them. That is allow to pass at least all LLVM test suite cases. <any relocation> / R_MIPS_SUB / R_MIPS_HI16 | R_MIPS_LO16 <any relocation> / R_MIPS_64 / R_MIPS_NONE The first relocation is a 'real' relocation which is calculated using the corresponding symbol's value. The second and the third relocations used to modify result of the first one: extend it to 64-bit, extract high or low part etc. For details, see part 2.9 'Relocation' at https://dmz-portal.mips.com/mw/images/8/82/007-4658-001.pdf llvm-svn: 268876
2016-05-08 22:08:40 +08:00
# REL: Relocations [
# REL-NEXT: ]
.text
.global __start
__start:
lui $gp,%hi(%neg(%gp_rel(__start))) # R_MIPS_GPREL16
# R_MIPS_SUB
# R_MIPS_HI16
loc:
daddiu $gp,$gp,%lo(%neg(%gp_rel(__start))) # R_MIPS_GPREL16
# R_MIPS_SUB
# R_MIPS_LO16
.section .rodata,"a",@progbits
.gpdword(loc) # R_MIPS_GPREL32
# R_MIPS_64