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-tls.s

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

124 lines
4.5 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] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
# Check MIPS TLS relocations handling.
# RUN: llvm-mc -filetype=obj -triple=mips-unknown-linux \
# RUN: %p/Inputs/mips-tls.s -o %t.so.o
[ELF][MIPS] Improve tests * Add --no-show-raw-insn to llvm-objdump -d tests * When linking an executable with %t.so, the path %t.so will be recorded in the DT_NEEDED entry if %t.so doesn't have DT_SONAME. .dynstr will have varying lengths on different systems. Add -soname to make tests more robust. llvm-svn: 366988
2019-07-25 15:12:23 +08:00
# RUN: ld.lld -shared %t.so.o -soname=t.so -o %t.so
[ELF][MIPS] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
# RUN: llvm-mc -filetype=obj -triple=mips-unknown-linux %s -o %t.o
[ELF][MIPS] Fix initialization of TLS-related GOT entries This patch allows static linking of TLS code. To do that it fixes GOT entries initialization. If TLS-related GOT entry created for a preemptible symbol i.e. has a corresponding dynamic relocation, leave the entry initialized by zero. Write down adjusted TLS symbol's values otherwise. For the adjustments calculation use offsets for thread-local storage. https://www.linux-mips.org/wiki/NPTL llvm-svn: 280914
2016-09-08 17:07:19 +08:00
[mips] Make another set of test cases more tolerant to exact symbol addresses. NFC llvm-svn: 371458
2019-09-10 06:04:20 +08:00
# RUN: echo "SECTIONS { \
# RUN: . = 0x10000; .text : { *(.text) } \
# RUN: . = 0x30000; .got : { *(.got) } \
# RUN: }" > %t.script
# RUN: ld.lld %t.o %t.so -script %t.script -o %t.exe
[mips] Use llvm-readobj `-A` flag in test cases. NFC llvm-svn: 373589
2019-10-03 20:08:04 +08:00
# RUN: llvm-objdump -d -s -t --no-show-raw-insn %t.exe \
# RUN: | FileCheck -check-prefix=DIS %s
# RUN: llvm-readobj -r -A %t.exe | FileCheck %s
[ELF][MIPS] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
[ELF][MIPS] Don't emit dynamic relocations for PIE non-preemptible TLS Whilst not wrong (unless using static PIE where the relocations are likely not implemented by the runtime), this is inefficient, as the TLS module indices and offsets are independent of the executable's load address. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101382
2021-04-28 01:57:47 +08:00
# RUN: ld.lld -pie %t.o %t.so -script %t.script -o %t.pie
# RUN: llvm-objdump -d -s -t --no-show-raw-insn %t.pie \
# RUN: | FileCheck -check-prefix=DIS %s
# RUN: llvm-readobj -r -A %t.pie | FileCheck %s
[mips] Make another set of test cases more tolerant to exact symbol addresses. NFC llvm-svn: 371458
2019-09-10 06:04:20 +08:00
# RUN: ld.lld -shared %t.o %t.so -script %t.script -o %t-out.so
[mips] Use llvm-readobj `-A` flag in test cases. NFC llvm-svn: 373589
2019-10-03 20:08:04 +08:00
# RUN: llvm-objdump -d -s -t --no-show-raw-insn %t-out.so \
# RUN: | FileCheck -check-prefix=DIS-SO %s
# RUN: llvm-readobj -r -A %t-out.so | FileCheck -check-prefix=SO %s
[ELF][MIPS] Fix initialization of TLS-related GOT entries This patch allows static linking of TLS code. To do that it fixes GOT entries initialization. If TLS-related GOT entry created for a preemptible symbol i.e. has a corresponding dynamic relocation, leave the entry initialized by zero. Write down adjusted TLS symbol's values otherwise. For the adjustments calculation use offsets for thread-local storage. https://www.linux-mips.org/wiki/NPTL llvm-svn: 280914
2016-09-08 17:07:19 +08:00
[llvm-objdump] Map STT_TLS to ST_Other (previously ST_Data) ST_Data is used to model BFD `BFD_OBJECT`. A STT_TLS symbol does not have the `BFD_OBJECT` flag in BFD. This makes sense because a STT_TLS symbol is like in a different address space, normal data/object properties do not apply on them. With this change, a STT_TLS symbol will not be displayed as 'O'. This new behavior matches objdump. Differential Revision: https://reviews.llvm.org/D96735
2021-02-18 15:17:20 +08:00
# DIS: 00000000 l .tdata 00000000 loc
# DIS: 00000000 *UND* 00000000 foo
# DIS: 00000004 g .tdata 00000000 bar
[ELF][MIPS] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
# DIS: Contents of section .got:
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# DIS-NEXT: 30000 00000000 80000000 00000000 ffff9000
# DIS-NEXT: 30010 ffff9004 00000000 00000000 00000001
# DIS-NEXT: 30020 00000000 00000001 ffff8004
[ELF][MIPS] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
[llvm-objdump] -d: print `00000000 <foo>:` instead of `00000000 foo:` The new behavior matches GNU objdump. A pair of angle brackets makes tests slightly easier. `.foo:` is not unique and thus cannot be used in a `CHECK-LABEL:` directive. Without `-LABEL`, the CHECK line can match the `Disassembly of section` line and causes the next `CHECK-NEXT:` to fail. ``` Disassembly of section .foo: 0000000000001634 .foo: ``` Bdragon: <> has metalinguistic connotation. it just "feels right" Reviewed By: rupprecht Differential Revision: https://reviews.llvm.org/D75713
2020-03-06 06:18:38 +08:00
# DIS: <__start>:
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# DIS-NEXT: addiu $2, $3, -32732
[llvm-objdump] Further rearrange llvm-objdump sections for compatability Summary: rL371826 rearranged some output from llvm-objdump for GNU objdump compatability, but there still seem to be some more. I think this rearrangement is a little closer. Overview of the ordering which matches GNU objdump: * Archive headers * File headers * Section headers * Symbol table * Dwarf debugging * Relocations (if `--disassemble` is not used) * Section contents * Disassembly Reviewers: jhenderson, justice_adams, grimar, ychen, espindola Reviewed By: jhenderson Subscribers: aprantl, emaste, arichardson, jrtc27, atanasyan, seiya, llvm-commits, MaskRay Tags: #llvm Differential Revision: https://reviews.llvm.org/D68066 llvm-svn: 373671
2019-10-04 06:01:08 +08:00
# DIS-NEXT: addiu $2, $3, -32744
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# DIS-NEXT: addiu $2, $3, -32724
[llvm-objdump] Further rearrange llvm-objdump sections for compatability Summary: rL371826 rearranged some output from llvm-objdump for GNU objdump compatability, but there still seem to be some more. I think this rearrangement is a little closer. Overview of the ordering which matches GNU objdump: * Archive headers * File headers * Section headers * Symbol table * Dwarf debugging * Relocations (if `--disassemble` is not used) * Section contents * Disassembly Reviewers: jhenderson, justice_adams, grimar, ychen, espindola Reviewed By: jhenderson Subscribers: aprantl, emaste, arichardson, jrtc27, atanasyan, seiya, llvm-commits, MaskRay Tags: #llvm Differential Revision: https://reviews.llvm.org/D68066 llvm-svn: 373671
2019-10-04 06:01:08 +08:00
# DIS-NEXT: addiu $2, $3, -32740
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# DIS-NEXT: addiu $2, $3, -32716
# DIS-NEXT: addiu $2, $3, -32736
[ELF][MIPS] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
# CHECK: Relocations [
# CHECK-NEXT: Section (7) .rel.dyn {
[llvm-readobj] - For SHT_REL relocations, don't display an addend. 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
2020-12-10 21:12:26 +08:00
# CHECK-NEXT: 0x30008 R_MIPS_TLS_TPREL32 foo
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# CHECK-NEXT: 0x30014 R_MIPS_TLS_DTPMOD32 foo
# CHECK-NEXT: 0x30018 R_MIPS_TLS_DTPREL32 foo
[ELF][MIPS] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
# CHECK-NEXT: }
# CHECK-NEXT: ]
[mips] Use llvm-readobj `-A` flag in test cases. NFC llvm-svn: 373589
2019-10-03 20:08:04 +08:00
# CHECK: Primary GOT {
[mips] Make another set of test cases more tolerant to exact symbol addresses. NFC llvm-svn: 371458
2019-09-10 06:04:20 +08:00
# CHECK-NEXT: Canonical gp value: 0x37FF0
[ELF][MIPS] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
# CHECK-NEXT: Reserved entries [
[ELF][MIPS] Fix initialization of TLS-related GOT entries This patch allows static linking of TLS code. To do that it fixes GOT entries initialization. If TLS-related GOT entry created for a preemptible symbol i.e. has a corresponding dynamic relocation, leave the entry initialized by zero. Write down adjusted TLS symbol's values otherwise. For the adjustments calculation use offsets for thread-local storage. https://www.linux-mips.org/wiki/NPTL llvm-svn: 280914
2016-09-08 17:07:19 +08:00
# CHECK: ]
[ELF][MIPS] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
# CHECK-NEXT: Local entries [
# CHECK-NEXT: ]
# CHECK-NEXT: Global entries [
# CHECK-NEXT: ]
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# CHECK-NEXT: Number of TLS and multi-GOT entries: 9
[ELF][MIPS] Multi-GOT implementation Almost all entries inside MIPS GOT are referenced by signed 16-bit index. Zero entry lies approximately in the middle of the GOT. So the total number of GOT entries cannot exceed ~16384 for 32-bit architecture and ~8192 for 64-bit architecture. This limitation makes impossible to link rather large application like for example LLVM+Clang. There are two workaround for this problem. The first one is using the -mxgot compiler's flag. It enables using a 32-bit index to access GOT entries. But each access requires two assembly instructions two load GOT entry index to a register. Another workaround is multi-GOT. This patch implements it. Here is a brief description of multi-GOT for detailed one see the following link https://dmz-portal.mips.com/wiki/MIPS_Multi_GOT. If the sum of local, global and tls entries is less than 64K only single got is enough. Otherwise, multi-got is created. Series of primary and multiple secondary GOTs have the following layout: ``` - Primary GOT Header Local entries Global entries Relocation only entries TLS entries - Secondary GOT Local entries Global entries TLS entries ... ``` All GOT entries required by relocations from a single input file entirely belong to either primary or one of secondary GOTs. To reference GOT entries each GOT has its own _gp value points to the "middle" of the GOT. In the code this value loaded to the register which is used for GOT access. MIPS 32 function's prologue: ``` lui v0,0x0 0: R_MIPS_HI16 _gp_disp addiu v0,v0,0 4: R_MIPS_LO16 _gp_disp ``` MIPS 64 function's prologue: ``` lui at,0x0 14: R_MIPS_GPREL16 main ``` Dynamic linker does not know anything about secondary GOTs and cannot use a regular MIPS mechanism for GOT entries initialization. So we have to use an approach accepted by other architectures and create dynamic relocations R_MIPS_REL32 to initialize global entries (and local in case of PIC code) in secondary GOTs. But ironically MIPS dynamic linker requires GOT entries and correspondingly ordered dynamic symbol table entries to deal with dynamic relocations. To handle this problem relocation-only section in the primary GOT contains entries for all symbols referenced in global parts of secondary GOTs. Although the sum of local and normal global entries of the primary got should be less than 64K, the size of the primary got (including relocation-only entries can be greater than 64K, because parts of the primary got that overflow the 64K limit are used only by the dynamic linker at dynamic link-time and not by 16-bit gp-relative addressing at run-time. The patch affects common LLD code in the following places: - Added new hidden -mips-got-size flag. This flag required to set low maximum size of a single GOT to be able to test the implementation using small test cases. - Added InputFile argument to the getRelocTargetVA function. The same symbol referenced by GOT relocation from different input file might be allocated in different GOT. So result of relocation depends on the file. - Added new ctor to the DynamicReloc class. This constructor records settings of dynamic relocation which used to adjust address of 64kb page lies inside a specific output section. With the patch LLD is able to link all LLVM+Clang+LLD applications and libraries for MIPS 32/64 targets. Differential revision: https://reviews.llvm.org/D31528 llvm-svn: 334390
2018-06-11 15:24:31 +08:00
# ^-- -32744 R_MIPS_TLS_GOTTPREL R_MIPS_TLS_TPREL32 foo
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# ^-- -32740 R_MIPS_TLS_GOTTPREL VA - 0x7000 loc
# ^-- -32736 R_MIPS_TLS_GOTTPREL VA - 0x7000 bar
# ^-- -32732 R_MIPS_TLS_GD R_MIPS_TLS_DTPMOD32 foo
# ^-- -32728 R_MIPS_TLS_DTPREL32 foo
# ^-- -32724 R_MIPS_TLS_LDM 1 loc
# ^-- -32720 0 loc
# ^-- -32716 R_MIPS_TLS_GD 1 bar
# ^-- -32712 VA - 0x8000 bar
[ELF][MIPS] Fix initialization of TLS-related GOT entries This patch allows static linking of TLS code. To do that it fixes GOT entries initialization. If TLS-related GOT entry created for a preemptible symbol i.e. has a corresponding dynamic relocation, leave the entry initialized by zero. Write down adjusted TLS symbol's values otherwise. For the adjustments calculation use offsets for thread-local storage. https://www.linux-mips.org/wiki/NPTL llvm-svn: 280914
2016-09-08 17:07:19 +08:00
# DIS-SO: Contents of section .got:
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# DIS-SO-NEXT: 30000 00000000 80000000 00000000 00000000
# DIS-SO-NEXT: 30010 00000004 00000000 00000000 00000000
# DIS-SO-NEXT: 30020 00000000 00000000 00000000
[ELF][MIPS] Fix initialization of TLS-related GOT entries This patch allows static linking of TLS code. To do that it fixes GOT entries initialization. If TLS-related GOT entry created for a preemptible symbol i.e. has a corresponding dynamic relocation, leave the entry initialized by zero. Write down adjusted TLS symbol's values otherwise. For the adjustments calculation use offsets for thread-local storage. https://www.linux-mips.org/wiki/NPTL llvm-svn: 280914
2016-09-08 17:07:19 +08:00
# SO: Relocations [
# SO-NEXT: Section (7) .rel.dyn {
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# SO-NEXT: 0x3000C R_MIPS_TLS_TPREL32 -
# SO-NEXT: 0x3001C R_MIPS_TLS_DTPMOD32 -
[llvm-readobj] - For SHT_REL relocations, don't display an addend. 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
2020-12-10 21:12:26 +08:00
# SO-NEXT: 0x30008 R_MIPS_TLS_TPREL32 foo
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# SO-NEXT: 0x30014 R_MIPS_TLS_DTPMOD32 foo
# SO-NEXT: 0x30018 R_MIPS_TLS_DTPREL32 foo
# SO-NEXT: 0x30010 R_MIPS_TLS_TPREL32 bar
# SO-NEXT: 0x30024 R_MIPS_TLS_DTPMOD32 bar
# SO-NEXT: 0x30028 R_MIPS_TLS_DTPREL32 bar
[ELF][MIPS] Fix initialization of TLS-related GOT entries This patch allows static linking of TLS code. To do that it fixes GOT entries initialization. If TLS-related GOT entry created for a preemptible symbol i.e. has a corresponding dynamic relocation, leave the entry initialized by zero. Write down adjusted TLS symbol's values otherwise. For the adjustments calculation use offsets for thread-local storage. https://www.linux-mips.org/wiki/NPTL llvm-svn: 280914
2016-09-08 17:07:19 +08:00
# SO-NEXT: }
# SO-NEXT: ]
[mips] Use llvm-readobj `-A` flag in test cases. NFC llvm-svn: 373589
2019-10-03 20:08:04 +08:00
# SO: Primary GOT {
[ELF] Simplify RelRo, TLS, NOBITS section ranks and make RW PT_LOAD start with RelRo Old: PT_LOAD(.data | PT_GNU_RELRO(.data.rel.ro .bss.rel.ro) | .bss) New: PT_LOAD(PT_GNU_RELRO(.data.rel.ro .bss.rel.ro) | .data .bss) The placement of | indicates page alignment caused by PT_GNU_RELRO. The new layout has simpler rules and saves space for many cases. Old size: roundup(.data) + roundup(.data.rel.ro) New size: roundup(.data.rel.ro + .bss.rel.ro) + .data Other advantages: * At runtime the 3 memory mappings decrease to 2. * start(PT_TLS) = start(PT_GNU_RELRO) = start(RW PT_LOAD). This simplifies binary manipulation tools. GNU strip before 2.31 discards PT_GNU_RELRO if its address is not equal to the start of its associated PT_LOAD. This has been fixed by https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f2731e0c374e5323ce4cdae2bcc7b7fe22da1a6f But with this change, we will be compatible with GNU strip before 2.31 * Before, .got.plt (non-relro by default) was placed before .got (relro by default), which made it impossible to have _GLOBAL_OFFSET_TABLE_ (start of .got.plt on x86-64) equal to the end of .got (R_GOT*_FROM_END) (https://bugs.llvm.org/show_bug.cgi?id=36555). With the new ordering, we can improve on this regard if we'd like to. Reviewers: ruiu, espindola, pcc Subscribers: emaste, arichardson, llvm-commits, joerg, jdoerfert Differential Revision: https://reviews.llvm.org/D56828 llvm-svn: 356117
2019-03-14 11:47:45 +08:00
# SO-NEXT: Canonical gp value: 0x37FF0
[ELF][MIPS] Fix initialization of TLS-related GOT entries This patch allows static linking of TLS code. To do that it fixes GOT entries initialization. If TLS-related GOT entry created for a preemptible symbol i.e. has a corresponding dynamic relocation, leave the entry initialized by zero. Write down adjusted TLS symbol's values otherwise. For the adjustments calculation use offsets for thread-local storage. https://www.linux-mips.org/wiki/NPTL llvm-svn: 280914
2016-09-08 17:07:19 +08:00
# SO-NEXT: Reserved entries [
# SO: ]
# SO-NEXT: Local entries [
# SO-NEXT: ]
# SO-NEXT: Global entries [
# SO-NEXT: ]
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# SO-NEXT: Number of TLS and multi-GOT entries: 9
[ELF][MIPS] Multi-GOT implementation Almost all entries inside MIPS GOT are referenced by signed 16-bit index. Zero entry lies approximately in the middle of the GOT. So the total number of GOT entries cannot exceed ~16384 for 32-bit architecture and ~8192 for 64-bit architecture. This limitation makes impossible to link rather large application like for example LLVM+Clang. There are two workaround for this problem. The first one is using the -mxgot compiler's flag. It enables using a 32-bit index to access GOT entries. But each access requires two assembly instructions two load GOT entry index to a register. Another workaround is multi-GOT. This patch implements it. Here is a brief description of multi-GOT for detailed one see the following link https://dmz-portal.mips.com/wiki/MIPS_Multi_GOT. If the sum of local, global and tls entries is less than 64K only single got is enough. Otherwise, multi-got is created. Series of primary and multiple secondary GOTs have the following layout: ``` - Primary GOT Header Local entries Global entries Relocation only entries TLS entries - Secondary GOT Local entries Global entries TLS entries ... ``` All GOT entries required by relocations from a single input file entirely belong to either primary or one of secondary GOTs. To reference GOT entries each GOT has its own _gp value points to the "middle" of the GOT. In the code this value loaded to the register which is used for GOT access. MIPS 32 function's prologue: ``` lui v0,0x0 0: R_MIPS_HI16 _gp_disp addiu v0,v0,0 4: R_MIPS_LO16 _gp_disp ``` MIPS 64 function's prologue: ``` lui at,0x0 14: R_MIPS_GPREL16 main ``` Dynamic linker does not know anything about secondary GOTs and cannot use a regular MIPS mechanism for GOT entries initialization. So we have to use an approach accepted by other architectures and create dynamic relocations R_MIPS_REL32 to initialize global entries (and local in case of PIC code) in secondary GOTs. But ironically MIPS dynamic linker requires GOT entries and correspondingly ordered dynamic symbol table entries to deal with dynamic relocations. To handle this problem relocation-only section in the primary GOT contains entries for all symbols referenced in global parts of secondary GOTs. Although the sum of local and normal global entries of the primary got should be less than 64K, the size of the primary got (including relocation-only entries can be greater than 64K, because parts of the primary got that overflow the 64K limit are used only by the dynamic linker at dynamic link-time and not by 16-bit gp-relative addressing at run-time. The patch affects common LLD code in the following places: - Added new hidden -mips-got-size flag. This flag required to set low maximum size of a single GOT to be able to test the implementation using small test cases. - Added InputFile argument to the getRelocTargetVA function. The same symbol referenced by GOT relocation from different input file might be allocated in different GOT. So result of relocation depends on the file. - Added new ctor to the DynamicReloc class. This constructor records settings of dynamic relocation which used to adjust address of 64kb page lies inside a specific output section. With the patch LLD is able to link all LLVM+Clang+LLD applications and libraries for MIPS 32/64 targets. Differential revision: https://reviews.llvm.org/D31528 llvm-svn: 334390
2018-06-11 15:24:31 +08:00
# ^-- -32744 R_MIPS_TLS_GOTTPREL R_MIPS_TLS_TPREL32 foo
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
# ^-- -32740 R_MIPS_TLS_GOTTPREL R_MIPS_TLS_TPREL32 loc
# ^-- -32736 R_MIPS_TLS_GOTTPREL R_MIPS_TLS_TPREL32 bar
# ^-- -32732 R_MIPS_TLS_GD R_MIPS_TLS_DTPMOD32 foo
# ^-- -32728 R_MIPS_TLS_DTPREL32 foo
# ^-- -32724 R_MIPS_TLS_LDM R_MIPS_TLS_DTPMOD32 loc
# ^-- -32720 0 loc
# ^-- -32716 R_MIPS_TLS_GD R_MIPS_TLS_DTPMOD32 bar
# ^-- -32712 R_MIPS_TLS_DTPREL32 bar
[ELF][MIPS] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
.text
.global __start
__start:
addiu $2, $3, %tlsgd(foo) # R_MIPS_TLS_GD
addiu $2, $3, %gottprel(foo) # R_MIPS_TLS_GOTTPREL
[ELF][MIPS] Fix initialization of TLS-related GOT entries This patch allows static linking of TLS code. To do that it fixes GOT entries initialization. If TLS-related GOT entry created for a preemptible symbol i.e. has a corresponding dynamic relocation, leave the entry initialized by zero. Write down adjusted TLS symbol's values otherwise. For the adjustments calculation use offsets for thread-local storage. https://www.linux-mips.org/wiki/NPTL llvm-svn: 280914
2016-09-08 17:07:19 +08:00
addiu $2, $3, %tlsldm(loc) # R_MIPS_TLS_LDM
[ELF][MIPS] Emit dynamic relocations for PIC non-preemptible static TLS This is the same problem as 127176e59eb9, but for static TLS rather than dynamic TLS. Although we know the symbol will be the one in our own TLS segment, and thus the offset of it within that, we don't know where in the static TLS block our data will be allocated and thus we must emit a dynamic relocation for this case. Reviewed By: MaskRay, atanasyan Differential Revision: https://reviews.llvm.org/D101381
2021-04-28 02:03:57 +08:00
addiu $2, $3, %gottprel(loc) # R_MIPS_TLS_GOTTPREL
[ELF][MIPS] Fix initialization of TLS-related GOT entries This patch allows static linking of TLS code. To do that it fixes GOT entries initialization. If TLS-related GOT entry created for a preemptible symbol i.e. has a corresponding dynamic relocation, leave the entry initialized by zero. Write down adjusted TLS symbol's values otherwise. For the adjustments calculation use offsets for thread-local storage. https://www.linux-mips.org/wiki/NPTL llvm-svn: 280914
2016-09-08 17:07:19 +08:00
addiu $2, $3, %tlsgd(bar) # R_MIPS_TLS_GD
addiu $2, $3, %gottprel(bar) # R_MIPS_TLS_GOTTPREL
[ELF][MIPS] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
.section .tdata,"awT",%progbits
[ELF][MIPS] Fix initialization of TLS-related GOT entries This patch allows static linking of TLS code. To do that it fixes GOT entries initialization. If TLS-related GOT entry created for a preemptible symbol i.e. has a corresponding dynamic relocation, leave the entry initialized by zero. Write down adjusted TLS symbol's values otherwise. For the adjustments calculation use offsets for thread-local storage. https://www.linux-mips.org/wiki/NPTL llvm-svn: 280914
2016-09-08 17:07:19 +08:00
.global bar
[ELF][MIPS] Support MIPS TLS relocations The patch adds one more partition to the MIPS GOT. This time it is for TLS related GOT entries. Such entries are located after 'local' and 'global' ones. We cannot get a final offset for these entries at the time of creation because we do not know size of 'local' and 'global' partitions. So we have to adjust the offset later using `getMipsTlsOffset()` method. All MIPS TLS relocations which need GOT entries operates MIPS style GOT offset - 'offset from the GOT's beginning' - MipsGPOffset constant. That is why I add new types of relocation expressions. One more difference from othe ABIs is that the MIPS ABI does not support any TLS relocation relaxations. I decided to make a separate function `handleMipsTlsRelocation` and put MIPS TLS relocation handling code there. It is similar to `handleTlsRelocation` routine and duplicates its code. But it allows to make the code cleaner and prevent pollution of the `handleTlsRelocation` by MIPS 'if' statements. Differential Revision: http://reviews.llvm.org/D21606 llvm-svn: 273569
2016-06-23 23:26:31 +08:00
loc:
.word 0
[ELF][MIPS] Fix initialization of TLS-related GOT entries This patch allows static linking of TLS code. To do that it fixes GOT entries initialization. If TLS-related GOT entry created for a preemptible symbol i.e. has a corresponding dynamic relocation, leave the entry initialized by zero. Write down adjusted TLS symbol's values otherwise. For the adjustments calculation use offsets for thread-local storage. https://www.linux-mips.org/wiki/NPTL llvm-svn: 280914
2016-09-08 17:07:19 +08:00
bar:
.word 0