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/sort-non-script.s

17 lines
480 B
ArmAsm
Raw Normal View History

Revert "Revert "Only restrict order if both sections are in the script."" This reverts commit r282021, bringing back r282015. The problem was that the comparison function was not a strict weak ordering anymore, which this patch fixes. Original message: Only restrict order if both sections are in the script. This matches gold and bfd behavior and is required to handle some scripts. The script has to assume where PT_LOADs start in order to align that spot. If we don't allow section it doesn't know about to move to the middle, we can need more PT_LOADs and those will not be aligned. llvm-svn: 282035
2016-09-21 06:43:15 +08:00
# REQUIRES: x86
[ELF] Change test files for style consistency. NFC * Move `REQUIRES:` line to the top * llvm-mc ... -o %t -> llvm-mc ... -o %t.o * Don't check "TEXT" "DATA" columns (they are bfd-style names that do not fit into llvm well) in llvm-objdump output llvm-svn: 335498
2018-06-26 01:07:40 +08:00
# RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %s -o %t.o
Revert "Revert "Only restrict order if both sections are in the script."" This reverts commit r282021, bringing back r282015. The problem was that the comparison function was not a strict weak ordering anymore, which this patch fixes. Original message: Only restrict order if both sections are in the script. This matches gold and bfd behavior and is required to handle some scripts. The script has to assume where PT_LOADs start in order to align that spot. If we don't allow section it doesn't know about to move to the middle, we can need more PT_LOADs and those will not be aligned. llvm-svn: 282035
2016-09-21 06:43:15 +08:00
# RUN: echo "SECTIONS { foo : {*(foo)} }" > %t.script
[ELF] Change test files for style consistency. NFC * Move `REQUIRES:` line to the top * llvm-mc ... -o %t -> llvm-mc ... -o %t.o * Don't check "TEXT" "DATA" columns (they are bfd-style names that do not fit into llvm well) in llvm-objdump output llvm-svn: 335498
2018-06-26 01:07:40 +08:00
# RUN: ld.lld --hash-style=sysv -o %t --script %t.script %t.o -shared
[ELF] Fix sort-non-script.s llvm-svn: 335499
2018-06-26 01:16:01 +08:00
# RUN: llvm-readelf -s %t | FileCheck %s
Revert "Revert "Only restrict order if both sections are in the script."" This reverts commit r282021, bringing back r282015. The problem was that the comparison function was not a strict weak ordering anymore, which this patch fixes. Original message: Only restrict order if both sections are in the script. This matches gold and bfd behavior and is required to handle some scripts. The script has to assume where PT_LOADs start in order to align that spot. If we don't allow section it doesn't know about to move to the middle, we can need more PT_LOADs and those will not be aligned. llvm-svn: 282035
2016-09-21 06:43:15 +08:00
[lld] Mitigate relocation overflow [part 1 of 2]. This CL places .dynsym and .dynstr at the beginning of SHF_ALLOC sections. We do this to mitigate the possibility that huge .dynsym and .dynstr sections placed between ro-data and text sections cause relocation overflow. Differential Revision: https://reviews.llvm.org/D45788 llvm-svn: 332374
2018-05-16 01:02:35 +08:00
# CHECK: .dynsym {{.*}} A
# CHECK-NEXT: .hash {{.*}} A
[ELF] Make non-writable non-executable PROGBITS sections closer to .text This generalizes the old heuristic placing SHT_DYNSYM SHT_DYNSTR first in the readonly SHF_ALLOC segment. Reviewers: espindola Subscribers: emaste, arichardson, llvm-commits Differential Revision: https://reviews.llvm.org/D48406 llvm-svn: 335674
2018-06-27 06:13:32 +08:00
# CHECK-NEXT: .dynstr {{.*}} A
[ELF] Assign RF_EXEC rank even if --no-rosegment or SECTIONS command is used Summary: Currently when --no-rosegment is specified or a linker script with SECTIONS command is used, .rodata (A) .text (AX) are assigned the same rank and .rodata may be placed after .text . This increases the gap between .text and .bss and can cause pc-relative relocation overflow (e.g. gcc crtbegin.o crtbegin.S have R_X86_64_PC32 relocation from .text to .bss). This patch makes SingleRoRx affect only segment layout, not section layout. As a consequence, .rodata will be placed before .text regardless of SingleRoRx. Reviewers: espindola, ruiu, grimar, echristo, javed.absar Subscribers: emaste, arichardson, llvm-commits Differential Revision: https://reviews.llvm.org/D48405 llvm-svn: 335627
2018-06-27 01:04:47 +08:00
# CHECK-NEXT: .text {{.*}} AX
Revert "Revert "Only restrict order if both sections are in the script."" This reverts commit r282021, bringing back r282015. The problem was that the comparison function was not a strict weak ordering anymore, which this patch fixes. Original message: Only restrict order if both sections are in the script. This matches gold and bfd behavior and is required to handle some scripts. The script has to assume where PT_LOADs start in order to align that spot. If we don't allow section it doesn't know about to move to the middle, we can need more PT_LOADs and those will not be aligned. llvm-svn: 282035
2016-09-21 06:43:15 +08:00
# CHECK-NEXT: foo {{.*}} WA
ELF: Place relro sections after non-relro sections in r/w segment. This is in preparation for my next change, which will introduce a relro nobits section. That requires that relro sections appear at the end of the progbits part of the r/w segment so that the relro nobits section can appear contiguously. Because of the amount of churn required in the test suite, I'm making this change separately. llvm-svn: 291523
2017-01-10 09:21:30 +08:00
# CHECK-NEXT: .dynamic {{.*}} WA
Revert "Revert "Only restrict order if both sections are in the script."" This reverts commit r282021, bringing back r282015. The problem was that the comparison function was not a strict weak ordering anymore, which this patch fixes. Original message: Only restrict order if both sections are in the script. This matches gold and bfd behavior and is required to handle some scripts. The script has to assume where PT_LOADs start in order to align that spot. If we don't allow section it doesn't know about to move to the middle, we can need more PT_LOADs and those will not be aligned. llvm-svn: 282035
2016-09-21 06:43:15 +08:00
.section foo, "aw"
.byte 0