Lines Matching refs:segments

207 example, the COFF version stamp, or the ELF program segments.  BFD
1408 * BFD ELF sections and segments::	ELF sections and segments
1415 @node BFD ELF sections and segments
1416 @subsection ELF sections and segments
1418 The ELF ABI permits a file to have either sections or segments or both.
1421 only program segments.
1429 ELF program segments are intended for fast interpretation by a system
1432 system loader will examine the program segments to decide how to load
1434 segments (type @samp{PT_LOAD}) are directly loaded into memory.  Other
1435 program segments are interpreted by the loader, and generally provide
1438 When an ELF file has both program segments and sections, an ELF program
1462 way to examine both sections and segments.  When BFD is used to open an
1465 ELF program segments.
1468 segments will be read to set the LMA of the sections.  This is because
1469 ELF sections only have a VMA, while ELF program segments have both a VMA
1470 and an LMA.  Any program segments will be copied by the
1472 @samp{print_private} entry point.  Otherwise, the program segments are
1474 access to the program segments.
1476 When BFD is used to create an executable, the program segments will be
1483 segments when creating an executable: the @samp{bfd_record_phdr}
1485 create program segments itself, but will only create the program
1486 segments specified by the caller.  The linker uses this function to
1515 than read the ELF program segments as BFD sections.
1713 sections.  Instead, they only have program segments.
1716 actually represent program segments.  Since ELF program segments do not
1733 program segments with the type @samp{PT_NOTE}.  BFD will attempt to
1734 interpret the information in these segments, and will create additional