| /netbsd-src/external/gpl3/binutils.old/dist/bfd/doc/ |
| H A D | bfd.texi | 15 This file documents the BFD library.
41 @settitle LIB BFD, the Binary File Descriptor Library
46 @subtitle First Edition---BFD version < 3.0 % Since no product is stable before version 3.0 :-)
58 \hfill {\it BFD}, \manvers\par
84 * Overview:: Overview of BFD
85 * BFD front end:: BFD front end
86 * BFD back ends:: BFD back ends
88 * BFD Index:: BFD Index
91 @node Overview, BFD front end, Top, Top
93 @cindex BFD
[all …]
|
| H A D | bfdint.texi | 5 @settitle BFD Internals
8 @title{BFD Internals}
15 This file documents the internals of the BFD library.
40 @top BFD Internals
44 This document describes some BFD internal information which may be
45 helpful when working on BFD. It is very incomplete.
53 * BFD overview:: BFD overview
54 * BFD guidelines:: BFD programming guidelines
55 * BFD target vector:: BFD target vector
56 * BFD generated files:: BFD generated files
[all …]
|
| H A D | bfdt.texi | 1 @node typedef bfd, Error reporting, BFD front end, BFD front end
3 A BFD has type @code{bfd}; objects of this type are the
4 cornerstone of any application using BFD. Using BFD
5 consists of making references though the BFD and to data in the BFD.
37 /* The filename the application opened the BFD with. */
44 to the file backing the BFD. */
54 BFD retains state information on the file here. */
60 /* A unique identifier of the BFD */
66 /* Values that may appear in the flags field of a BFD. These also
75 /* BFD contains relocation entries. */
[all …]
|
| H A D | archive.texi | 5 An archive (or library) is just another BFD. It has a symbol
8 The big difference between an archive BFD and an ordinary BFD
21 A BFD returned by @code{bfd_openr_next_archived_file} can be
24 return the same BFD. If you close the archive BFD, then all
28 @code{archive_next} pointer in a BFD. The first one is findable
30 @code{bfd_set_archive_head} (q.v.). A given BFD may be in only
33 As expected, the BFD archive code is more general than the
34 archive code of any given environment. BFD archives may
57 Archives are supported in BFD in @code{archive.c}.
99 Provided a BFD, @var{archive}, containing an archive and NULL, open
[all …]
|
| H A D | bfdsumm.texi | 1 @c This summary of BFD is shared by the BFD and LD docs.
4 When an object file is opened, BFD subroutines automatically determine
10 BFD reads from different sections of the file and processes them.
12 tables. Each BFD back end provides a routine for converting
16 relevant BFD back end which reads and converts the table into a canonical
19 another BFD back end routine is called to take the newly
23 * BFD information loss:: Information Loss
24 * Canonical format:: The BFD canonical object-file format
27 @node BFD information loss
31 supported by BFD do not provide identical facilities, and
[all …]
|
| H A D | format.texi | 2 A format is a BFD concept of high level file contents type. The
3 formats supported by BFD are:
10 The BFD may contain data, symbols, relocations and debug info.
17 The BFD contains other BFDs and an optional index.
24 The BFD contains the result of an executable core dump.
36 Verify if the file attached to the BFD @var{abfd} is compatible
40 If the BFD has been set to a specific target before the
97 This function sets the file format of the BFD @var{abfd} to the
98 format @var{format}. If the target set in the BFD does not
99 support the format requested, the format is invalid, or the BFD
|
| H A D | syms.texi | 2 BFD tries to maintain as much symbol information as it can when
3 it moves information from file to file. BFD passes information
5 application requests the symbol table, BFD reads the table in
12 a BFD is read in. On output, the coff back end can reconstruct
14 information unique to coff which BFD doesn't know or
17 would be lost. The symbol table of a BFD
19 made. Then the BFD back end fills in a table provided by the
21 output symbols, the application provides BFD with a table of
35 There are two stages to reading a symbol table from a BFD:
66 connected to the BFD; it is freed when the BFD is closed.
[all …]
|
| H A D | opncls.texi | 21 Return a pointer to the created BFD. If @var{fd} is not -1,
29 The new BFD is marked as cacheable iff @var{fd} is -1.
38 BFD. It can be accessed via the bfd_get_filename() macro.
48 @var{target}. Return a pointer to the created BFD.
58 BFD. It can be accessed via the bfd_get_filename() macro.
68 @code{fopen}. It opens a BFD on a file already described by the
73 cached by BFD (opened as needed, closed as needed to free
76 call bfd_set_cacheable(bfd, 1) on the returned BFD. The default
78 until @code{bfd_close}, and will not be affected by BFD operations
87 BFD. It can be accessed via the bfd_get_filename() macro.
[all …]
|
| H A D | targets.texi | 5 Each port of BFD to a different machine requires the creation
7 part of BFD is a structure containing pointers to functions
8 which perform certain low level operations on files. BFD
13 target are unknown. BFD uses various mechanisms to determine
19 Create a BFD by calling the internal routine
21 target string supplied to @code{bfd_openr} and the new BFD pointer.
31 as the target type, and set @code{target_defaulted} in the BFD to
46 @code{bfd_open_file}, and returns the BFD.
48 Once the BFD has been opened and the target selected, the file
50 @code{bfd_check_format} on the BFD with a suggested format.
[all …]
|
| H A D | cache.texi | 2 The file caching mechanism is embedded within BFD and allows
9 the required BFD is open. If not, then it chooses a file to
23 Add a newly opened BFD to the cache.
32 Remove the BFD @var{abfd} from the cache. If the attached file is open,
62 BFD so that future accesses know the file is open. If the @code{FILE *}
|
| H A D | bfd.info | 11 This file documents the BFD library.
40 * Overview:: Overview of BFD
41 * BFD front end:: BFD front end
42 * BFD back ends:: BFD back ends
44 * BFD Index:: BFD Index
47 File: bfd.info, Node: Overview, Next: BFD front end, Prev: Top, Up: Top
52 BFD is a package which allows applications to use the same routines to
54 file format can be supported simply by creating a new BFD back end and
57 BFD is split into two parts: the front end, and the back ends (one
59 * The front end of BFD provides the interface to the user. It manages
[all …]
|
| /netbsd-src/external/gpl3/binutils/dist/bfd/doc/ |
| H A D | bfd.texi | 15 This file documents the BFD library.
41 @settitle LIB BFD, the Binary File Descriptor Library
46 @subtitle First Edition---BFD version < 3.0 % Since no product is stable before version 3.0 :-)
58 \hfill {\it BFD}, \manvers\par
84 * Overview:: Overview of BFD
85 * BFD front end:: BFD front end
86 * BFD back ends:: BFD back ends
88 * BFD Index:: BFD Index
91 @node Overview, BFD front end, Top, Top
93 @cindex BFD
[all …]
|
| H A D | bfdt.texi | 1 @node typedef bfd, Error reporting, BFD front end, BFD front end
3 A BFD has type @code{bfd}; objects of this type are the
4 cornerstone of any application using BFD. Using BFD
5 consists of making references though the BFD and to data in the BFD.
15 /* The filename the application opened the BFD with. */
22 to the file backing the BFD. */
32 BFD retains state information on the file here. */
38 /* A unique identifier of the BFD */
44 /* Values that may appear in the flags field of a BFD. These also
53 /* BFD contains relocation entries. */
[all …]
|
| H A D | bfdint.texi | 5 @settitle BFD Internals
8 @title{BFD Internals}
15 This file documents the internals of the BFD library.
40 @top BFD Internals
44 This document describes some BFD internal information which may be
45 helpful when working on BFD. It is very incomplete.
53 * BFD overview:: BFD overview
54 * BFD guidelines:: BFD programming guidelines
55 * BFD target vector:: BFD target vector
56 * BFD generated files:: BFD generated files
[all …]
|
| H A D | opncls.texi | 10 Return a new BFD. All BFD's are allocated through this routine.
16 Allocate a new BFD as a member of archive OBFD.
29 Return a pointer to the created BFD. If @var{fd} is not -1,
37 The new BFD is marked as cacheable iff @var{fd} is -1.
46 BFD. It can be accessed via the bfd_get_filename() macro.
53 @var{target}. Return a pointer to the created BFD.
63 BFD. It can be accessed via the bfd_get_filename() macro.
70 @code{fopen}. It opens a BFD on a file already described by the
75 cached by BFD (opened as needed, closed as needed to free
78 call bfd_set_cacheable(bfd, 1) on the returned BFD. The default
[all …]
|
| H A D | archive.texi | 4 An archive (or library) is just another BFD. It has a symbol
7 The big difference between an archive BFD and an ordinary BFD
20 A BFD returned by @code{bfd_openr_next_archived_file} can be
23 return the same BFD. If you close the archive BFD, then all
27 @code{archive_next} pointer in a BFD. The first one is findable
29 @code{bfd_set_archive_head} (q.v.). A given BFD may be in only
32 As expected, the BFD archive code is more general than the
33 archive code of any given environment. BFD archives may
56 Archives are supported in BFD in @code{archive.c}.
87 Provided a BFD, @var{archive}, containing an archive and NULL, open
[all …]
|
| H A D | bfdsumm.texi | 1 @c This summary of BFD is shared by the BFD and LD docs.
4 When an object file is opened, BFD subroutines automatically determine
10 BFD reads from different sections of the file and processes them.
12 tables. Each BFD back end provides a routine for converting
16 relevant BFD back end which reads and converts the table into a canonical
19 another BFD back end routine is called to take the newly
23 * BFD information loss:: Information Loss
24 * Canonical format:: The BFD canonical object-file format
27 @node BFD information loss
31 supported by BFD do not provide identical facilities, and
[all …]
|
| H A D | format.texi | 2 A format is a BFD concept of high level file contents type. The
3 formats supported by BFD are:
10 The BFD may contain data, symbols, relocations and debug info.
17 The BFD contains other BFDs and an optional index.
24 The BFD contains the result of an executable core dump.
32 Verify if the file attached to the BFD @var{abfd} is compatible
36 If the BFD has been set to a specific target before the
86 This function sets the file format of the BFD @var{abfd} to the
87 format @var{format}. If the target set in the BFD does not
88 support the format requested, the format is invalid, or the BFD
|
| H A D | syms.texi | 2 BFD tries to maintain as much symbol information as it can when
3 it moves information from file to file. BFD passes information
5 application requests the symbol table, BFD reads the table in
12 a BFD is read in. On output, the coff back end can reconstruct
14 information unique to coff which BFD doesn't know or
17 would be lost. The symbol table of a BFD
19 made. Then the BFD back end fills in a table provided by the
21 output symbols, the application provides BFD with a table of
35 There are two stages to reading a symbol table from a BFD:
66 connected to the BFD; it is freed when the BFD is closed.
[all …]
|
| H A D | targets.texi | 4 Each port of BFD to a different machine requires the creation
6 part of BFD is a structure containing pointers to functions
7 which perform certain low level operations on files. BFD
12 target are unknown. BFD uses various mechanisms to determine
18 Create a BFD by calling the internal routine
20 target string supplied to @code{bfd_openr} and the new BFD pointer.
30 as the target type, and set @code{target_defaulted} in the BFD to
45 @code{bfd_open_file}, and returns the BFD.
47 Once the BFD has been opened and the target selected, the file
49 @code{bfd_check_format} on the BFD with a suggested format.
[all …]
|
| H A D | cache.texi | 2 The file caching mechanism is embedded within BFD and allows
9 the required BFD is open. If not, then it chooses a file to
19 Add a newly opened BFD to the cache.
25 Remove the BFD @var{abfd} from the cache. If the attached file is open,
37 close a BFD even if it is not marked as being cacheable, ie
55 BFD so that future accesses know the file is open. If the @code{FILE *}
|
| H A D | bfd.info | 3 This file documents the BFD library.
36 * Overview:: Overview of BFD
37 * BFD front end:: BFD front end
38 * BFD back ends:: BFD back ends
40 * BFD Index:: BFD Index
43 File: bfd.info, Node: Overview, Next: BFD front end, Prev: Top, Up: Top
48 BFD is a package which allows applications to use the same routines to
50 file format can be supported simply by creating a new BFD back end and
53 BFD is split into two parts: the front end, and the back ends (one
55 • The front end of BFD provides the interface to the user. It
[all …]
|
| H A D | coffcode.texi | 2 BFD supports a number of different flavours of coff format.
31 You can verify that your new BFD backend works quite simply by
87 However, as a GNU extension, BFD can generate executable images
95 The functionality is supported in BFD by code implemented under
112 new BFD, the flag is set to the default for the target format. This
113 information can be used by a client of the BFD library when deciding
114 what output format to generate, and means that a BFD that is opened
115 for read and subsequently converted to a writeable BFD and modified
127 Each flavour of coff supported in BFD has its own header file
143 moment. To port BFD, that person will have to add more @code{#defines}.
[all …]
|
| /netbsd-src/external/gpl3/binutils/dist/bfd/ |
| H A D | README | 1 BFD is an object file library. It permits applications to use the
4 BFD is used by the GNU debugger, assembler, linker, and the binary
7 The documentation on using BFD is scanty and may be occasionally
11 There is some BFD internals documentation in doc/bfdint.texi which may
12 help programmers who want to modify BFD.
14 BFD is normally built as part of another package. See the build
18 BFD supports the following configure options:
32 Build BFD as a shared library.
37 Report bugs in BFD to https://sourceware.org/bugzilla/
43 systems. Remember that BFD must support cross compilation from any
|
| /netbsd-src/external/gpl3/binutils.old/dist/bfd/ |
| H A D | README | 1 BFD is an object file library. It permits applications to use the
4 BFD is used by the GNU debugger, assembler, linker, and the binary
7 The documentation on using BFD is scanty and may be occasionally
11 There is some BFD internals documentation in doc/bfdint.texi which may
12 help programmers who want to modify BFD.
14 BFD is normally built as part of another package. See the build
18 BFD supports the following configure options:
32 Build BFD as a shared library.
37 Report bugs in BFD to https://sourceware.org/bugzilla/
43 systems. Remember that BFD must support cross compilation from any
|