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/string-table.s

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

28 lines
632 B
ArmAsm
Raw Normal View History

[ELF] Move `// REQUIRES:` line to the top llvm-svn: 335676
2018-06-27 06:20:04 +08:00
// REQUIRES: x86
ELF: Create a string table. For now only the sections are in it, but it already makes the output easier to read and test. llvm-svn: 244702
2015-08-12 08:00:24 +08:00
// RUN: llvm-mc -filetype=obj -triple=x86_64-unknown-linux %s -o %t
Rename ld.lld2 to ld.lld since it is the default. llvm-svn: 253437
2015-11-18 14:11:01 +08:00
// RUN: ld.lld %t -o %t2
[test] Change llvm-readobj -long-option to --long-option or well-known short options. NFC Also change some options that have different semantics (cause confusion) in llvm-readelf mode: -s => -S -t => --symbols -sd => --section-data llvm-svn: 359651
2019-05-01 13:49:01 +08:00
// RUN: llvm-readobj --sections %t2 | FileCheck %s
ELF: Create a string table. For now only the sections are in it, but it already makes the output easier to read and test. llvm-svn: 244702
2015-08-12 08:00:24 +08:00
.global _start
_start:
Change which input sections we concatenate After Mark's patch I was wondering what was the rationale for the ELF spec requiring us to merge only sections with matching flags and types. I tried emailing https://groups.google.com/forum/#!forum/generic-abi, but looks like my emails are not being posted (the list is probably moderated). I emailed Cary Coutant instead. Cary pointed out that the section was a late addition and didn't got the scrutiny it deserved. Given that and the problems found by implementing the letter of the standard, I propose changing lld to merge all sections with the same name and issue errors if the types or some critical flags are different. This should allow an unmodified firefox linked with lld to run. This also merges some code with the linkerscript path. llvm-svn: 291107
2017-01-05 22:20:35 +08:00
.section foobar,"",@progbits
Take name, type and flags in consideration when concatenating sections. This is mandated by the ELF spec. llvm-svn: 244911
2015-08-14 01:04:50 +08:00
Place SHF_ALLOC sections first in the output. Having them in the middle of the file complicates the creation of segments. llvm-svn: 244898
2015-08-13 23:23:46 +08:00
.section bar, "a"
Include non-alloca sections in the link. llvm-svn: 244895
2015-08-13 22:45:44 +08:00
Place SHF_ALLOC sections first in the output. Having them in the middle of the file complicates the creation of segments. llvm-svn: 244898
2015-08-13 23:23:46 +08:00
// Both sections are in the output and that the alloc section is first:
// CHECK: Name: bar
Take name, type and flags in consideration when concatenating sections. This is mandated by the ELF spec. llvm-svn: 244911
2015-08-14 01:04:50 +08:00
// CHECK-NEXT: Type: SHT_PROGBITS
// CHECK-NEXT: Flags [
// CHECK-NEXT: SHF_ALLOC
// CHECK-NEXT: ]
lld: Default image base address to 0x200000 on x86-64 Align to the large page size (known as a superpage or huge page). FreeBSD automatically promotes large, superpage-aligned allocations. Differential Revision: https://reviews.llvm.org/D27042 llvm-svn: 287782
2016-11-24 01:44:02 +08:00
// CHECK-NEXT: Address: 0x200120
Place SHF_ALLOC sections first in the output. Having them in the middle of the file complicates the creation of segments. llvm-svn: 244898
2015-08-13 23:23:46 +08:00
// CHECK: Name: foobar
Take name, type and flags in consideration when concatenating sections. This is mandated by the ELF spec. llvm-svn: 244911
2015-08-14 01:04:50 +08:00
// CHECK-NEXT: Type: SHT_PROGBITS
// CHECK-NEXT: Flags [
// CHECK-NEXT: ]
// CHECK-NEXT: Address: 0x0
// CHECK-NOT: Name: foobar