a7a447be0f
Imagine we have a YAML declaration of few sections: `foo1`, `<unnamed 2>`, `foo3`, `foo4`. To put them into segment we can do (1*): ``` Sections: - Section: foo1 - Section: foo4 ``` or we can use (2*): ``` Sections: - Section: foo1 - Section: foo3 - Section: foo4 ``` or (3*) : ``` Sections: - Section: foo1 ## "(index 2)" here is a name that we automatically created for a unnamed section. - Section: (index 2) - Section: foo3 - Section: foo4 ``` It looks really confusing that we don't have to list all of sections. At first I've tried to make this rule stricter and report an error when there is a gap (i.e. when a section is included into segment, but not listed explicitly). This did not work perfect, because such approach conflicts with unnamed sections/fills (see (3*)). This patch drops "Sections" key and introduces 2 keys instead: `FirstSec` and `LastSec`. Both are optional. Differential revision: https://reviews.llvm.org/D90458
33 lines
800 B
Plaintext
33 lines
800 B
Plaintext
# RUN: yaml2obj %s -o %t
|
|
# RUN: llvm-objcopy -R .note -O binary %t %t2
|
|
# RUN: od -Ax -t x1 %t2 | FileCheck %s
|
|
|
|
!ELF
|
|
FileHeader:
|
|
Class: ELFCLASS64
|
|
Data: ELFDATA2LSB
|
|
Type: ET_EXEC
|
|
Machine: EM_X86_64
|
|
Sections:
|
|
- Name: .note
|
|
Type: SHT_PROGBITS
|
|
Flags: [ SHF_ALLOC ]
|
|
Address: 0x1000
|
|
AddressAlign: 0x1000
|
|
Content: "32323232"
|
|
Size: 32
|
|
- Name: .rodata
|
|
Flags: [ SHF_ALLOC ]
|
|
Type: SHT_PROGBITS
|
|
Address: 0x1020
|
|
Size: 4064
|
|
Content: "DEADBEEF"
|
|
ProgramHeaders:
|
|
- Type: PT_LOAD
|
|
Flags: [ PF_R ]
|
|
VAddr: 0x1000
|
|
FirstSec: .note
|
|
LastSec: .rodata
|
|
|
|
# CHECK: 000000 de ad be ef
|