1@c This summary of BFD is shared by the BFD and LD docs.
2When an object file is opened, BFD subroutines automatically determine
3the format of the input object file. They then build a descriptor in
4memory with pointers to routines that will be used to access elements of
5the object file's data structures.
6
| 1@c This summary of BFD is shared by the BFD and LD docs.
2When an object file is opened, BFD subroutines automatically determine
3the format of the input object file. They then build a descriptor in
4memory with pointers to routines that will be used to access elements of
5the object file's data structures.
6
|
7As different information from the the object files is required,
| 7As different information from the object files is required,
|
8BFD reads from different sections of the file and processes them.
9For example, a very common operation for the linker is processing symbol
10tables. Each BFD back end provides a routine for converting
11between the object file's representation of symbols and an internal
12canonical format. When the linker asks for the symbol table of an object
13file, it calls through a memory pointer to the routine from the
14relevant BFD back end which reads and converts the table into a canonical
15form. The linker then operates upon the canonical form. When the link is
--- 133 unchanged lines hidden --- | 8BFD reads from different sections of the file and processes them.
9For example, a very common operation for the linker is processing symbol
10tables. Each BFD back end provides a routine for converting
11between the object file's representation of symbols and an internal
12canonical format. When the linker asks for the symbol table of an object
13file, it calls through a memory pointer to the routine from the
14relevant BFD back end which reads and converts the table into a canonical
15form. The linker then operates upon the canonical form. When the link is
--- 133 unchanged lines hidden --- |