Lines Matching refs:BFD
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
95 BFD is a package which allows applications to use the
98 creating a new BFD back end and adding it to the library.
100 BFD is split into two parts: the front end, and the back ends (one for
103 @item The front end of BFD provides the interface to the user. It manages
106 @item The back ends provide BFD its view of the real world. Each back
107 end provides a set of calls which the BFD front end can use to maintain
114 * What BFD Version 2 Can Do:: What BFD Version 2 Can Do
120 One spur behind BFD was the desire, on the part of the GNU 960 team at
127 said ``BFD''. Stallman was right, but the name stuck.
133 BFD was first implemented by members of Cygnus Support; Steve
140 @node How It Works, What BFD Version 2 Can Do, History, Overview
141 @section How To Use BFD
145 BFD provides a common interface to the parts of an object file
151 @file{bfd.h}. Our convention is to call this pointer a BFD, and
153 the target object file are applied as methods to the BFD. The mapping is
158 return the number of sections in an object file attached to a BFD
173 The abstraction used within BFD is that an object file has:
191 @node What BFD Version 2 Can Do, , How It Works, Overview
192 @section What BFD Version 2 Can Do
195 @node BFD front end, BFD back ends, Overview, Top
196 @chapter BFD Front End
222 @node Memory Usage, Initialization, Miscellaneous, BFD front end
224 BFD keeps all of its internal structures in obstacks. There is one obstack
225 per open BFD file, into which the current state is stored. When a BFD is
227 allocated by BFD for the closing file is thrown away.
229 BFD does not free anything created by an application, but pointers into
236 The general rule is to not close a BFD until all operations dependent
237 upon data from the BFD have been completed, or all the data from within
240 in obstacks associated with the supplied BFD. This could be used to
241 select the greediest open BFD, close it to reclaim the memory, perform
242 some operation and reopen the BFD again, to get a fresh copy of the data
245 @node Initialization, Sections, Memory Usage, BFD front end
248 @node Sections, Symbols, Initialization, BFD front end
251 @node Symbols, Archives, Sections, BFD front end
254 @node Archives, Formats, Symbols, BFD front end
257 @node Formats, Relocations, Archives, BFD front end
260 @node Relocations, Core Files, Formats, BFD front end
263 @node Core Files, Targets, Relocations, BFD front end
266 @node Targets, Architectures, Core Files, BFD front end
269 @node Architectures, Opening and Closing, Targets, BFD front end
272 @node Opening and Closing, Internal, Architectures, BFD front end
275 @node Internal, File Caching, Opening and Closing, BFD front end
278 @node File Caching, Linker Functions, Internal, BFD front end
281 @node Linker Functions, Hash Tables, File Caching, BFD front end
284 @node Hash Tables, , Linker Functions, BFD front end
287 @node BFD back ends, GNU Free Documentation License, BFD front end, Top
288 @chapter BFD back ends
301 @node What to Put Where, aout, BFD back ends, BFD back ends
303 All of BFD lives in one directory.
305 @node aout, coff, What to Put Where, BFD back ends
308 @node coff, elf, aout, BFD back ends
311 @node elf, mmo, coff, BFD back ends
316 @node mmo, , elf, BFD back ends
319 @node GNU Free Documentation License, BFD Index, BFD back ends, Top
322 @node BFD Index, , GNU Free Documentation License, Top
323 @unnumbered BFD Index