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

57 lines
1.5 KiB
ArmAsm
Raw Normal View History

Add support for merging string from SHF_STRINGS sections. llvm-svn: 251212
2015-10-25 06:51:01 +08:00
// REQUIRES: x86
// RUN: llvm-mc -filetype=obj -triple=x86_64-pc-linux %s -o %t.o
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 -o %t.so -shared
Add support for merging strings with alignment larger than one char. This reduces the .rodata of scyladb from 4501932 to 4334639 bytes (1.038 times smaller). I don't think it is critical to support tail merging, just exact duplicates, but given the code organization it was actually a bit easier to support both. llvm-svn: 261327
2016-02-19 22:17:40 +08:00
// RUN: llvm-readobj -s -section-data %t.so | FileCheck %s
Add support for merging string from SHF_STRINGS sections. llvm-svn: 251212
2015-10-25 06:51:01 +08:00
Add support for merging strings with alignment larger than one char. This reduces the .rodata of scyladb from 4501932 to 4334639 bytes (1.038 times smaller). I don't think it is critical to support tail merging, just exact duplicates, but given the code organization it was actually a bit easier to support both. llvm-svn: 261327
2016-02-19 22:17:40 +08:00
.section .rodata.foo,"aMS",@progbits,1
Add support for merging string from SHF_STRINGS sections. llvm-svn: 251212
2015-10-25 06:51:01 +08:00
.align 16
.asciz "foo"
Add support for merging strings with alignment larger than one char. This reduces the .rodata of scyladb from 4501932 to 4334639 bytes (1.038 times smaller). I don't think it is critical to support tail merging, just exact duplicates, but given the code organization it was actually a bit easier to support both. llvm-svn: 261327
2016-02-19 22:17:40 +08:00
.section .rodata.foo2,"aMS",@progbits,1
.align 16
Add support for merging string from SHF_STRINGS sections. llvm-svn: 251212
2015-10-25 06:51:01 +08:00
.asciz "foo"
Add support for merging strings with alignment larger than one char. This reduces the .rodata of scyladb from 4501932 to 4334639 bytes (1.038 times smaller). I don't think it is critical to support tail merging, just exact duplicates, but given the code organization it was actually a bit easier to support both. llvm-svn: 261327
2016-02-19 22:17:40 +08:00
.section .rodata.bar,"aMS",@progbits,1
.align 16
.asciz "bar"
Add support for merging string from SHF_STRINGS sections. llvm-svn: 251212
2015-10-25 06:51:01 +08:00
// CHECK: Name: .rodata
// CHECK-NEXT: Type: SHT_PROGBITS
// CHECK-NEXT: Flags [
// CHECK-NEXT: SHF_ALLOC
// CHECK-NEXT: SHF_MERGE
// CHECK-NEXT: SHF_STRINGS
// CHECK-NEXT: ]
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
// CHECK-NEXT: Address:
// CHECK-NEXT: Offset:
Add support for merging strings with alignment larger than one char. This reduces the .rodata of scyladb from 4501932 to 4334639 bytes (1.038 times smaller). I don't think it is critical to support tail merging, just exact duplicates, but given the code organization it was actually a bit easier to support both. llvm-svn: 261327
2016-02-19 22:17:40 +08:00
// CHECK-NEXT: Size: 20
Add support for merging string from SHF_STRINGS sections. llvm-svn: 251212
2015-10-25 06:51:01 +08:00
// CHECK-NEXT: Link: 0
// CHECK-NEXT: Info: 0
// CHECK-NEXT: AddressAlignment: 16
Add support for merging strings with alignment larger than one char. This reduces the .rodata of scyladb from 4501932 to 4334639 bytes (1.038 times smaller). I don't think it is critical to support tail merging, just exact duplicates, but given the code organization it was actually a bit easier to support both. llvm-svn: 261327
2016-02-19 22:17:40 +08:00
// CHECK-NEXT: EntrySize:
// CHECK-NEXT: SectionData (
// CHECK-NEXT: 0000: 666F6F00 00000000 00000000 00000000 |foo.............|
// CHECK-NEXT: 0010: 62617200 |bar.|
// CHECK-NEXT: )
Replace MergeOutputSection with a synthetic section. With a synthetic merge section we can have, for example, a single .rodata section with stings, fixed sized constants and non merge constants. I can be simplified further by not setting Entsize, but that is probably better done is a followup patch. This should allow some cleanup in the linker script code now that every output section command maps to just one output section. llvm-svn: 294005
2017-02-03 21:06:18 +08:00
.section .rodata2,"aMS",@progbits,1
Add support for merging strings with alignment larger than one char. This reduces the .rodata of scyladb from 4501932 to 4334639 bytes (1.038 times smaller). I don't think it is critical to support tail merging, just exact duplicates, but given the code organization it was actually a bit easier to support both. llvm-svn: 261327
2016-02-19 22:17:40 +08:00
.asciz "foo"
Add support for merging string from SHF_STRINGS sections. llvm-svn: 251212
2015-10-25 06:51:01 +08:00
Replace MergeOutputSection with a synthetic section. With a synthetic merge section we can have, for example, a single .rodata section with stings, fixed sized constants and non merge constants. I can be simplified further by not setting Entsize, but that is probably better done is a followup patch. This should allow some cleanup in the linker script code now that every output section command maps to just one output section. llvm-svn: 294005
2017-02-03 21:06:18 +08:00
// CHECK: Name: .rodata2
Add support for merging string from SHF_STRINGS sections. llvm-svn: 251212
2015-10-25 06:51:01 +08:00
// CHECK-NEXT: Type: SHT_PROGBITS
// CHECK-NEXT: Flags [
// CHECK-NEXT: SHF_ALLOC
// CHECK-NEXT: SHF_MERGE
// CHECK-NEXT: SHF_STRINGS
// CHECK-NEXT: ]
Handle 0 sized sections like any other section. This is a case where there is inconsistency among ELF linkers: * The spec says nothing special about empty sections. * BFD ld removes them. * Gold handles them like regular sections. We were outputting them but sometimes ignoring them. This would create odd looking outputs where a rw section could be in a ro segment for example. The bfd way of doing things is also strange for the case where a symbol points to the empty section. Now we match gold and what seems to be the intention of the spec. llvm-svn: 251988
2015-11-04 06:08:08 +08:00
// CHECK-NEXT: Address:
// CHECK-NEXT: Offset:
Add support for merging string from SHF_STRINGS sections. llvm-svn: 251212
2015-10-25 06:51:01 +08:00
// CHECK-NEXT: Size: 4
// CHECK-NEXT: Link: 0
// CHECK-NEXT: Info: 0
// CHECK-NEXT: AddressAlignment: 1
Add support for merging strings with alignment larger than one char. This reduces the .rodata of scyladb from 4501932 to 4334639 bytes (1.038 times smaller). I don't think it is critical to support tail merging, just exact duplicates, but given the code organization it was actually a bit easier to support both. llvm-svn: 261327
2016-02-19 22:17:40 +08:00
// CHECK-NEXT: EntrySize:
// CHECK-NEXT: SectionData (
// CHECK-NEXT: 0000: 666F6F00 |foo.|
// CHECK-NEXT: )