forked from OSchip/llvm-project
06456daa9e
Currently there is no way to describe the data that is not a part of an output section.
It can be a data used to align sections or to fill the gaps with something,
or another kind of custom data. In this patch I suggest a way to describe it. It looks like that:
```
Sections:
- Type: CustomFiller
Pattern: "CCDD"
Size: 4
- Name: .bar
Type: SHT_PROGBITS
Content: "FF"
```
I.e. I've added a kind of synthetic section with a synthetic type "CustomFiller".
In the code it is called a "SyntheticFiller", which is "a synthetic section which
might be used to write the custom data around regular output sections. It does
not present in the sections header table, but it might affect the output file size and
program headers produced. Think about it as about piece of data."
`SyntheticFiller` currently has a `Pattern` field and a `Size` field + an optional `Name`.
When written, `Size` of bytes in the output will be filled with a `Pattern`.
It is possible to reference a named filler it by name from the program headers description,
just like any other normal section.
Differential revision: https://reviews.llvm.org/D69709
|
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| COFFEmitter.cpp | ||
| COFFYAML.cpp | ||
| CodeViewYAMLDebugSections.cpp | ||
| CodeViewYAMLSymbols.cpp | ||
| CodeViewYAMLTypeHashing.cpp | ||
| CodeViewYAMLTypes.cpp | ||
| DWARFEmitter.cpp | ||
| DWARFVisitor.cpp | ||
| DWARFVisitor.h | ||
| DWARFYAML.cpp | ||
| ELFEmitter.cpp | ||
| ELFYAML.cpp | ||
| LLVMBuild.txt | ||
| MachOEmitter.cpp | ||
| MachOYAML.cpp | ||
| MinidumpEmitter.cpp | ||
| MinidumpYAML.cpp | ||
| ObjectYAML.cpp | ||
| WasmEmitter.cpp | ||
| WasmYAML.cpp | ||
| XCOFFYAML.cpp | ||
| YAML.cpp | ||
| yaml2obj.cpp | ||