Lines Matching refs:an
120 The first use is to read an object file. The object file readers are
122 These programs use BFD to view an object file in a generic form. The
125 The second use is to write an object file. The object file writers are
127 create an object file. The official BFD interface is normally adequate
135 linker, @samp{ld}. Originally, @samp{ld} was an object file reader and
136 an object file writer, and it did the link operation using the generic
177 section has a name and a size. Most sections also have an associated
184 relocation describes an action which the linker must take to modify the
185 section contents. Relocations have a symbol, an address, an addend, and
190 symbol has a name, a pointer to a section, an offset within that
194 represents an archive file as a file which contains a list of
209 printing, or linking an object file. The BFD support for a particular
320 The name of the target vector. This is an arbitrary string. This is
388 example, an a.out compiler will typically generate the symbol
394 The padding character to use at the end of an archive name. Normally
398 The maximum length of a short name in an archive. Normally @samp{14}.
441 by the @samp{bfd_check_format} function when examining an existing BFD.
451 specific information required to write out an object file or whatever of
458 should not be an array selected by format type, as the
527 corresponds to an actual section in an actual BFD.
619 Given a core file and a BFD for an executable, this returns whether the
651 Build and return an extended name table if one is needed to write out
658 This copies a file name into an archive header, truncating it as
672 Read and parse an archive header. This handles expanding the archive
679 Given an archive and a BFD representing a file stored within the
686 Given an archive and an index, return a BFD for the file in the archive
692 Do a stat on an element of an archive, returning information read from
698 After the entire contents of an archive have been written out, update
728 Create an empty symbol for the BFD. This is needed because most targets
730 larger than an @samp{asymbol} and storing the extra information at the
732 what looks like a pointer to an empty @samp{asymbol}. This is called
771 Given an address within a section, use the debugging information to find
856 is normally used to align the first section at an efficient position on
881 Given an object file or an archive, add all symbols into the linker
1127 @samp{ARCH_SIZE} to an appropriate value. There are no 64 bit NLM
1164 A relocation is an action which the linker must take when linking. It
1167 created by the assembler when it creates an object file.
1177 Slightly more complex relocations may include an addend, which is a
1200 In BFD, each section has an array of @samp{arelent} structures. Each
1201 structure has a pointer to a symbol, an address within the section, an
1211 field to use as an escape.
1230 @samp{bfd_perform_relocation} was written to handle relocations on an
1257 So, if you want to add a new target, or add a new relocation to an
1271 symbol, possibly with an addend, possibly adding the symbol value to the
1283 Test the assembler. Consider the cases of relocation against an
1298 overflow, use a linker script to force an overflow and make sure the
1317 happening when an input file in a different format has relocations.
1339 assembler to create an @samp{arelent} structure, it has to be able to
1373 the case of an assembly, a relocatable link, and a final link. At
1374 least one special function would be defined as an escape, and it might
1382 would provide some mechanism (a function pointer or an initial
1430 loader. They have a type, a VMA, an LMA, file contents, and a couple of
1431 other fields. When an ELF executable is run on a Unix system, the
1438 When an ELF file has both program segments and sections, an ELF program
1446 system loader will load an entire program segment at a time.
1462 way to examine both sections and segments. When BFD is used to open an
1467 When BFD is used to examine an object file or executable, any program
1470 and an LMA. Any program segments will be copied by the
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}
1562 Define @samp{ELF_ARCH} to the BFD architecture (an element of the
1576 in an embedded system, or which has no memory management hardware, this
1594 representing @samp{a}, with an addend that gives the offset from the
1598 instructions to load an address, then the addend may not fit in a single
1618 takes an @samp{arelent} and a @samp{Rel} or @samp{Rela} structure, and
1622 an index into a table of howto structures.
1657 an ELF file the linker will not need to convert symbols and relocations,
1715 When BFD is used to read an ELF core file, the BFD sections will
1720 A single ELF program segment may include both an initialized part and an
1739 BFD does not currently provide any way to create an ELF core file. In
1810 Another name for an ELF shared library.
1830 NetWare Loadable Module. Used to describe the format of an object which
1836 information. Normally produced by an assembler.
1839 The format of an object file. Typically object files and executables
1869 referred to as the symbol table. A symbol is basically a name and an
1874 program will have an associated symbol.
1890 an executable is run. Compare with LMA, above.