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/no-space.s

25 lines
889 B
ArmAsm
Raw Normal View History

Error out instead of producing a corrupt PT_LOAD. What bfd and gold do is give up in putting the headers in the PT_LOAD and just start the PT_LOAD in the second page. llvm-svn: 281660
2016-09-16 05:22:11 +08:00
# REQUIRES: x86
# RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %s -o %t.o
# RUN: echo "SECTIONS {foo 0 : {*(foo*)} }" > %t.script
Don't error if we can't put the header in a PT_LOAD. If there is not sufficient address space, just give up and don't put the header in the PT_LOAD. This matches bfd behaviour and I found at least one script that depends on having a section at address 0. llvm-svn: 282750
2016-09-30 02:50:34 +08:00
# RUN: ld.lld -o %t --script %t.script %t.o -shared
# RUN: llvm-readobj -elf-output-style=GNU -l %t | FileCheck %s
Error out instead of producing a corrupt PT_LOAD. What bfd and gold do is give up in putting the headers in the PT_LOAD and just start the PT_LOAD in the second page. llvm-svn: 281660
2016-09-16 05:22:11 +08:00
Start linker scripts at 0. We were implicitly creating space for the headers. That is not the behaviour of bfd, which requires the script to use SIZEOF_HEADERS. The difference is important for scripts that don't use SIZEOF_HEADERS and expect the first section to be at 0. llvm-svn: 282818
2016-09-30 08:16:11 +08:00
# RUN: echo "SECTIONS {foo : {*(foo*)} }" > %t.script
# RUN: ld.lld -o %t --script %t.script %t.o -shared
# RUN: llvm-readobj -elf-output-style=GNU -l %t | FileCheck %s
Don't error if we can't put the header in a PT_LOAD. If there is not sufficient address space, just give up and don't put the header in the PT_LOAD. This matches bfd behaviour and I found at least one script that depends on having a section at address 0. llvm-svn: 282750
2016-09-30 02:50:34 +08:00
# There is not enough address space available for the header, so just start the PT_LOAD
Don't create a bogus PT_PHDR if we don't allocate the headers. llvm-svn: 292644
2017-01-21 04:46:15 +08:00
# after it. Don't create a PT_PHDR as the header is not allocated.
Don't error if we can't put the header in a PT_LOAD. If there is not sufficient address space, just give up and don't put the header in the PT_LOAD. This matches bfd behaviour and I found at least one script that depends on having a section at address 0. llvm-svn: 282750
2016-09-30 02:50:34 +08:00
# CHECK: Program Headers:
# CHECK-NEXT: Type Offset VirtAddr PhysAddr
# CHECK-NEXT: LOAD 0x001000 0x0000000000000000 0x0000000000000000
# CHECK: Section to Segment mapping:
# CHECK-NEXT: Segment Sections...
Don't create a bogus PT_PHDR if we don't allocate the headers. llvm-svn: 292644
2017-01-21 04:46:15 +08:00
# CHECK-NEXT: 00 foo .text .dynsym .hash .dynstr
Error out instead of producing a corrupt PT_LOAD. What bfd and gold do is give up in putting the headers in the PT_LOAD and just start the PT_LOAD in the second page. llvm-svn: 281660
2016-09-16 05:22:11 +08:00
.section foo, "a"
.quad 0