Lines Matching refs:sections
11 The document is split in four sections:
256 carrying the various sets of structures (and data) in the ELF sections under
262 Earlier design attempted to ineptly explain the relations of the ELF sections
270 * One or more .text sections.
271 * Zero or more read-only data sections.
272 * Zero or more data sections.
273 * Relocations for each of these sections.
275 It may also have some architecture-specific sections. For example:
280 * Relocations for each of these sections.
283 and handles the architecture-specifc sections as needed. This process is much
286 The payload contains at least three sections:
844 with -ffunction-sections / -fdata-sections. Changes would have to
871 ### .rodata sections
898 ### .bss and .data sections.
904 (.data or .rodata section changes), or even to .bss sections.
906 As such the ELF payload can introduce new .rodata, .bss, and .data sections.
964 * Be able to patch .rodata, .bss, and .data sections.
1014 to limitations of a hotpatching framework (init-sections, parts of
1091 ### .bss and .data sections.
1105 and the .data or .bss sections are of zero length.