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/linkerscript/tbss.s

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

44 lines
1.5 KiB
ArmAsm
Raw Normal View History

Add a test showing we handle .tbss sections in linker scripts. llvm-svn: 281496
2016-09-15 00:40:33 +08:00
# REQUIRES: x86
# RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %s -o %t.o
[ELF] Make dot in .tbss correct GNU ld doesn't support multiple SHF_TLS SHT_NOBITS output sections (it restores the address after an SHF_TLS SHT_NOBITS section, so consecutive SHF_TLS SHT_NOBITS sections will have conflicting address ranges). That said, `threadBssOffset` implements limited support for consecutive SHF_TLS SHT_NOBITS sections. (SHF_TLS SHT_PROGBITS following a SHF_TLS SHT_NOBITS can still be incorrect.) `.` in an output section description of an SHF_TLS SHT_NOBITS section is incorrect. (https://lists.llvm.org/pipermail/llvm-dev/2021-July/151974.html) This patch saves the end address of the previous tbss section in `ctx->tbssAddr`, changes `dot` in the beginning of `assignOffset` so that `.` evaluation will be correct. Reviewed By: peter.smith Differential Revision: https://reviews.llvm.org/D107208
2021-08-04 23:58:50 +08:00
# RUN: echo 'SECTIONS { \
Don't depend on lld creating space for the headers. Currently lld will implicitly reserve space for the headers. This is not the case is bfd, where it is the script responsibility to use SIZEOF_HEADERS. This means that a script not using SIZEOF_HEADERS and expecting the address of the first section to be 0 would fail with lld. I am fixing that is the next commit. This one just makes the tests explicitly use SIZEOF_HEADERS to avoid the dependency on the current behaviour. llvm-svn: 282814
2016-09-30 08:06:24 +08:00
# RUN: . = SIZEOF_HEADERS; \
# RUN: .text : { *(.text) } \
[ELF] Make dot in .tbss correct GNU ld doesn't support multiple SHF_TLS SHT_NOBITS output sections (it restores the address after an SHF_TLS SHT_NOBITS section, so consecutive SHF_TLS SHT_NOBITS sections will have conflicting address ranges). That said, `threadBssOffset` implements limited support for consecutive SHF_TLS SHT_NOBITS sections. (SHF_TLS SHT_PROGBITS following a SHF_TLS SHT_NOBITS can still be incorrect.) `.` in an output section description of an SHF_TLS SHT_NOBITS section is incorrect. (https://lists.llvm.org/pipermail/llvm-dev/2021-July/151974.html) This patch saves the end address of the previous tbss section in `ctx->tbssAddr`, changes `dot` in the beginning of `assignOffset` so that `.` evaluation will be correct. Reviewed By: peter.smith Differential Revision: https://reviews.llvm.org/D107208
2021-08-04 23:58:50 +08:00
# RUN: .tbss : { __tbss_start = .; *(.tbss) __tbss_end = .; } \
# RUN: second_tbss : { second_tbss_start = .; *(second_tbss) second_tbss_end = .; } \
Don't depend on lld creating space for the headers. Currently lld will implicitly reserve space for the headers. This is not the case is bfd, where it is the script responsibility to use SIZEOF_HEADERS. This means that a script not using SIZEOF_HEADERS and expecting the address of the first section to be 0 would fail with lld. I am fixing that is the next commit. This one just makes the tests explicitly use SIZEOF_HEADERS to avoid the dependency on the current behaviour. llvm-svn: 282814
2016-09-30 08:06:24 +08:00
# RUN: bar : { *(bar) } \
[ELF] Make dot in .tbss correct GNU ld doesn't support multiple SHF_TLS SHT_NOBITS output sections (it restores the address after an SHF_TLS SHT_NOBITS section, so consecutive SHF_TLS SHT_NOBITS sections will have conflicting address ranges). That said, `threadBssOffset` implements limited support for consecutive SHF_TLS SHT_NOBITS sections. (SHF_TLS SHT_PROGBITS following a SHF_TLS SHT_NOBITS can still be incorrect.) `.` in an output section description of an SHF_TLS SHT_NOBITS section is incorrect. (https://lists.llvm.org/pipermail/llvm-dev/2021-July/151974.html) This patch saves the end address of the previous tbss section in `ctx->tbssAddr`, changes `dot` in the beginning of `assignOffset` so that `.` evaluation will be correct. Reviewed By: peter.smith Differential Revision: https://reviews.llvm.org/D107208
2021-08-04 23:58:50 +08:00
# RUN: }' > %t.lds
# RUN: ld.lld -T %t.lds %t.o -o %t1
# RUN: llvm-readelf -S -s %t1 | FileCheck %s
Add a test showing we handle .tbss sections in linker scripts. llvm-svn: 281496
2016-09-15 00:40:33 +08:00
[ELF] Make dot in .tbss correct GNU ld doesn't support multiple SHF_TLS SHT_NOBITS output sections (it restores the address after an SHF_TLS SHT_NOBITS section, so consecutive SHF_TLS SHT_NOBITS sections will have conflicting address ranges). That said, `threadBssOffset` implements limited support for consecutive SHF_TLS SHT_NOBITS sections. (SHF_TLS SHT_PROGBITS following a SHF_TLS SHT_NOBITS can still be incorrect.) `.` in an output section description of an SHF_TLS SHT_NOBITS section is incorrect. (https://lists.llvm.org/pipermail/llvm-dev/2021-July/151974.html) This patch saves the end address of the previous tbss section in `ctx->tbssAddr`, changes `dot` in the beginning of `assignOffset` so that `.` evaluation will be correct. Reviewed By: peter.smith Differential Revision: https://reviews.llvm.org/D107208
2021-08-04 23:58:50 +08:00
# RUN: echo 'PHDRS { text PT_LOAD; }' > %th.lds
# RUN: cat %th.lds %t.lds > %t2.lds
# RUN: ld.lld -T %t.lds %t.o -o %t2
# RUN: llvm-readelf -S -s %t2 | FileCheck %s
Add a test showing we handle .tbss sections in linker scripts. llvm-svn: 281496
2016-09-15 00:40:33 +08:00
[ELF] Make dot in .tbss correct GNU ld doesn't support multiple SHF_TLS SHT_NOBITS output sections (it restores the address after an SHF_TLS SHT_NOBITS section, so consecutive SHF_TLS SHT_NOBITS sections will have conflicting address ranges). That said, `threadBssOffset` implements limited support for consecutive SHF_TLS SHT_NOBITS sections. (SHF_TLS SHT_PROGBITS following a SHF_TLS SHT_NOBITS can still be incorrect.) `.` in an output section description of an SHF_TLS SHT_NOBITS section is incorrect. (https://lists.llvm.org/pipermail/llvm-dev/2021-July/151974.html) This patch saves the end address of the previous tbss section in `ctx->tbssAddr`, changes `dot` in the beginning of `assignOffset` so that `.` evaluation will be correct. Reviewed By: peter.smith Differential Revision: https://reviews.llvm.org/D107208
2021-08-04 23:58:50 +08:00
## Test that a tbss section doesn't affect the start address of the next section.
Add a test showing we handle .tbss sections in linker scripts. llvm-svn: 281496
2016-09-15 00:40:33 +08:00
[ELF] Make dot in .tbss correct GNU ld doesn't support multiple SHF_TLS SHT_NOBITS output sections (it restores the address after an SHF_TLS SHT_NOBITS section, so consecutive SHF_TLS SHT_NOBITS sections will have conflicting address ranges). That said, `threadBssOffset` implements limited support for consecutive SHF_TLS SHT_NOBITS sections. (SHF_TLS SHT_PROGBITS following a SHF_TLS SHT_NOBITS can still be incorrect.) `.` in an output section description of an SHF_TLS SHT_NOBITS section is incorrect. (https://lists.llvm.org/pipermail/llvm-dev/2021-July/151974.html) This patch saves the end address of the previous tbss section in `ctx->tbssAddr`, changes `dot` in the beginning of `assignOffset` so that `.` evaluation will be correct. Reviewed By: peter.smith Differential Revision: https://reviews.llvm.org/D107208
2021-08-04 23:58:50 +08:00
# CHECK: Name Type Address Off Size ES Flg
# CHECK: .tbss NOBITS [[#%x,ADDR:]] [[#%x,OFF:]] 000004 00 WAT
# CHECK: second_tbss NOBITS {{0+}}[[#%x,ADDR+4]] {{0+}}[[#%x,OFF]] 000001 00 WAT
# CHECK: bar PROGBITS {{0+}}[[#%x,ADDR]] {{0+}}[[#%x,OFF]] 000004 00 WA
## Test that . in a tbss section represents the current location, even if the
## address will be reset.
# CHECK: Value {{.*}} Name
# CHECK: {{0+}}[[#%x,ADDR]] {{.*}} __tbss_start
# CHECK: {{0+}}[[#%x,ADDR+4]] {{.*}} __tbss_end
# CHECK: {{0+}}[[#%x,ADDR+4]] {{.*}} second_tbss_start
# CHECK: {{0+}}[[#%x,ADDR+5]] {{.*}} second_tbss_end
.globl _start
_start:
nop
.section .tbss,"awT",@nobits
.long 0
.section second_tbss,"awT",@nobits
.byte 0
.section bar, "aw"
.long 0