| /openbsd-src/gnu/usr.bin/binutils/bfd/doc/ |
| H A D | bfd.texinfo | 31 This file documents the BFD library.
54 @settitle LIB BFD, the Binary File Descriptor Library
59 @subtitle First Edition---BFD version < 3.0 % Since no product is stable berfore version 3.0 :-)
71 \hfill {\it BFD}, \manvers\par
96 * Overview:: Overview of BFD
97 * BFD front end:: BFD front end
98 * BFD back ends:: BFD back ends
103 @node Overview, BFD front end, Top, Top
105 @cindex BFD
107 BFD is a package which allows applications to use the
[all …]
|
| H A D | bfdint.texi | 7 @settitle BFD Internals
10 @title{BFD Internals}
17 @top BFD Internals
21 This document describes some BFD internal information which may be
22 helpful when working on BFD. It is very incomplete.
30 * BFD overview:: BFD overview
31 * BFD guidelines:: BFD programming guidelines
32 * BFD target vector:: BFD target vector
33 * BFD generated files:: BFD generated files
34 * BFD multiple compilations:: Files compiled multiple times in BFD
[all …]
|
| H A D | opncls.texi | 12 @var{target}. Return a pointer to the created BFD.
29 @code{fopen}. It opens a BFD on a file already described by the
34 cached by BFD (opened as needed, closed as needed to free
37 call bfd_set_cacheable(bfd, 1) on the returned BFD. The default
39 until @code{bfd_close}, and will not be affected by BFD operations
52 Open a BFD for read access on an existing stdio stream. When
53 the BFD is passed to @code{bfd_close}, the stream will be closed.
62 Create a BFD, associated with file @var{filename}, using the
75 Close a BFD. If the BFD was open for writing, then pending
80 All memory attached to the BFD is released.
[all …]
|
| H A D | bfdt.texi | 2 A BFD has type @code{bfd}; objects of this type are the
3 cornerstone of any application using BFD. Using BFD
4 consists of making references though the BFD and to data in the BFD.
15 /* A unique identifier of the BFD */
18 /* The filename the application opened the BFD with. */
38 BFD was opened. This is used to select which matching algorithm
46 /* When a file is closed by the caching routines, BFD retains
63 /* The format which belongs to the BFD. (object, core, etc.) */
66 /* The direction with which the BFD was opened. */
107 /* Symbol table for output BFD (with symcount entries). */
[all …]
|
| H A D | bfdsumm.texi | 1 @c This summary of BFD is shared by the BFD and LD docs.
2 When an object file is opened, BFD subroutines automatically determine
8 BFD reads from different sections of the file and processes them.
10 tables. Each BFD back end provides a routine for converting
14 relevant BFD back end which reads and converts the table into a canonical
17 another BFD back end routine is called to take the newly
21 * BFD information loss:: Information Loss
22 * Canonical format:: The BFD canonical object-file format
25 @node BFD information loss
29 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.
33 Verify if the file attached to the BFD @var{abfd} is compatible
37 If the BFD has been set to a specific target before the
94 This function sets the file format of the BFD @var{abfd} to the
95 format @var{format}. If the target set in the BFD does not
96 support the format requested, the format is invalid, or the BFD
|
| 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
22 @code{next} pointer in a BFD. The first one is findable through
24 @code{bfd_set_archive_head} (q.v.). A given BFD may be in only one
27 As expected, the BFD archive code is more general than the
28 archive code of any given environment. BFD archives may
51 Archives are supported in BFD in @code{archive.c}.
90 Provided a BFD, @var{archive}, containing an archive and NULL, open
91 an input BFD on the first contained element and returns that.
94 BFD to the next contained element. NULL is returned when there
|
| 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 | 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 | 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
29 Zero, or a pointer to the topmost BFD on the chain. This is
36 Check to see if the required BFD is the same as the last one
37 looked up. If so, then it can use the stream in the BFD with
54 Add a newly opened BFD to the cache.
63 Remove the BFD @var{abfd} from the cache. If the attached file is open,
79 BFD so that future accesses know the file is open. If the @code{FILE *}
|
| H A D | archures.texi | 2 BFD keeps one atom in a BFD describing the
3 architecture of the data attached to the BFD: a pointer to a
6 Pointers to structures can be requested independently of a BFD
8 without access to an open BFD.
16 When BFD starts up, all the architectures are called with an
22 BFD's idea of an architecture is implemented in @file{archures.c}.
308 within BFD.
353 Figure out if BFD supports any cpu which could be described with
365 of all the valid BFD architectures. Do not modify the names.
386 generic state. A BFD starts life by pointing to this
[all …]
|
| H A D | init.texi | 2 These are the functions that handle initializing a BFD.
11 This routine must be called before any other BFD function to
|
| /openbsd-src/gnu/usr.bin/binutils-2.17/bfd/doc/ |
| H A D | bfd.texinfo | 18 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 berfore version 3.0 :-)
58 \hfill {\it BFD}, \manvers\par
83 * Overview:: Overview of BFD
84 * BFD front end:: BFD front end
85 * BFD back ends:: BFD back ends
90 @node Overview, BFD front end, Top, Top
92 @cindex BFD
94 BFD is a package which allows applications to use the
[all …]
|
| H A D | bfdint.texi | 7 @settitle BFD Internals
10 @title{BFD Internals}
17 @top BFD Internals
21 This document describes some BFD internal information which may be
22 helpful when working on BFD. It is very incomplete.
30 * BFD overview:: BFD overview
31 * BFD guidelines:: BFD programming guidelines
32 * BFD target vector:: BFD target vector
33 * BFD generated files:: BFD generated files
34 * BFD multiple compilations:: Files compiled multiple times in BFD
[all …]
|
| H A D | bfdt.texi | 2 A BFD has type @code{bfd}; objects of this type are the
3 cornerstone of any application using BFD. Using BFD
4 consists of making references though the BFD and to data in the BFD.
15 /* A unique identifier of the BFD */
18 /* The filename the application opened the BFD with. */
25 to the file backing the BFD. */
34 BFD was opened. This is used to select which matching algorithm
42 /* When a file is closed by the caching routines, BFD retains
59 /* The format which belongs to the BFD. (object, core, etc.) */
62 /* The direction with which the BFD was opened. */
[all …]
|
| H A D | bfdsumm.texi | 1 @c This summary of BFD is shared by the BFD and LD docs.
2 When an object file is opened, BFD subroutines automatically determine
8 BFD reads from different sections of the file and processes them.
10 tables. Each BFD back end provides a routine for converting
14 relevant BFD back end which reads and converts the table into a canonical
17 another BFD back end routine is called to take the newly
21 * BFD information loss:: Information Loss
22 * Canonical format:: The BFD canonical object-file format
25 @node BFD information loss
29 supported by BFD do not provide identical facilities, and
[all …]
|
| H A D | opncls.texi | 16 Return a pointer to the created BFD. If @var{fd} is not -1,
24 The new BFD is marked as cacheable iff @var{fd} is -1.
38 @var{target}. Return a pointer to the created BFD.
55 @code{fopen}. It opens a BFD on a file already described by the
60 cached by BFD (opened as needed, closed as needed to free
63 call bfd_set_cacheable(bfd, 1) on the returned BFD. The default
65 until @code{bfd_close}, and will not be affected by BFD operations
78 Open a BFD for read access on an existing stdio stream. When
79 the BFD is passed to @code{bfd_close}, the stream will be closed.
98 Create and return a BFD backed by a read-only @var{stream}.
[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 | 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 | 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
22 @code{next} pointer in a BFD. The first one is findable through
24 @code{bfd_set_archive_head} (q.v.). A given BFD may be in only one
27 As expected, the BFD archive code is more general than the
28 archive code of any given environment. BFD archives may
51 Archives are supported in BFD in @code{archive.c}.
93 Provided a BFD, @var{archive}, containing an archive and NULL, open
94 an input BFD on the first contained element and returns that.
97 BFD to the next contained element. NULL is returned when there
|
| 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 | 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 | archures.texi | 2 BFD keeps one atom in a BFD describing the
3 architecture of the data attached to the BFD: a pointer to a
6 Pointers to structures can be requested independently of a BFD
8 without access to an open BFD.
16 When BFD starts up, all the architectures are called with an
22 BFD's idea of an architecture is implemented in @file{archures.c}.
359 within BFD.
404 Figure out if BFD supports any cpu which could be described with
416 of all the valid BFD architectures. Do not modify the names.
437 generic state. A BFD starts life by pointing to this
[all …]
|
| /openbsd-src/gnu/usr.bin/binutils-2.17/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 with BFD to bug-binutils@gnu.org.
43 systems. Remember that BFD must support cross compilation from any
|
| /openbsd-src/gnu/usr.bin/binutils/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 with BFD to bug-binutils@gnu.org.
43 systems. Remember that BFD must support cross compilation from any
|