Lines Matching refs:BFD
32 This file documents the BFD library.
55 @settitle LIB BFD, the Binary File Descriptor Library
60 @subtitle First Edition---BFD version < 3.0 % Since no product is stable berfore version 3.0 :-)
72 \hfill {\it BFD}, \manvers\par
97 * Overview:: Overview of BFD
98 * BFD front end:: BFD front end
99 * BFD back ends:: BFD back ends
104 @node Overview, BFD front end, Top, Top
106 @cindex BFD
108 BFD is a package which allows applications to use the
111 creating a new BFD back end and adding it to the library.
113 BFD is split into two parts: the front end, and the back ends (one for
116 @item The front end of BFD provides the interface to the user. It manages
119 @item The back ends provide BFD its view of the real world. Each back
120 end provides a set of calls which the BFD front end can use to maintain
127 * What BFD Version 2 Can Do:: What BFD Version 2 Can Do
133 One spur behind BFD was the desire, on the part of the GNU 960 team at
140 said ``BFD''. Stallman was right, but the name stuck.
146 BFD was first implemented by members of Cygnus Support; Steve
153 @node How It Works, What BFD Version 2 Can Do, History, Overview
154 @section How To Use BFD
158 BFD provides a common interface to the parts of an object file
164 @file{bfd.h}. Our convention is to call this pointer a BFD, and
166 the target object file are applied as methods to the BFD. The mapping is
171 return the number of sections in an object file attached to a BFD
186 The abstraction used within BFD is that an object file has:
204 @node What BFD Version 2 Can Do, , How It Works, Overview
205 @section What BFD Version 2 Can Do
208 @node BFD front end, BFD back ends, Overview, Top
209 @chapter BFD Front End
231 @node Memory Usage, Initialization, BFD front end, BFD front end
233 BFD keeps all of its internal structures in obstacks. There is one obstack
234 per open BFD file, into which the current state is stored. When a BFD is
236 allocated by BFD for the closing file is thrown away.
238 BFD does not free anything created by an application, but pointers into
245 The general rule is to not close a BFD until all operations dependent
246 upon data from the BFD have been completed, or all the data from within
249 in obstacks associated with the supplied BFD. This could be used to
250 select the greediest open BFD, close it to reclaim the memory, perform
251 some operation and reopen the BFD again, to get a fresh copy of the data
254 @node Initialization, Sections, Memory Usage, BFD front end
257 @node Sections, Symbols, Initialization, BFD front end
260 @node Symbols, Archives, Sections, BFD front end
263 @node Archives, Formats, Symbols, BFD front end
266 @node Formats, Relocations, Archives, BFD front end
269 @node Relocations, Core Files, Formats, BFD front end
272 @node Core Files, Targets, Relocations, BFD front end
275 @node Targets, Architectures, Core Files, BFD front end
278 @node Architectures, Opening and Closing, Targets, BFD front end
281 @node Opening and Closing, Internal, Architectures, BFD front end
284 @node Internal, File Caching, Opening and Closing, BFD front end
287 @node File Caching, Linker Functions, Internal, BFD front end
290 @node Linker Functions, Hash Tables, File Caching, BFD front end
293 @node Hash Tables, , Linker Functions, BFD front end
296 @node BFD back ends, GNU Free Documentation License, BFD front end, Top
297 @chapter BFD back ends
310 @node What to Put Where, aout, BFD back ends, BFD back ends
311 All of BFD lives in one directory.
313 @node aout, coff, What to Put Where, BFD back ends
316 @node coff, elf, aout, BFD back ends
319 @node elf, mmo, coff, BFD back ends
324 @node mmo, , elf, BFD back ends
327 @node GNU Free Documentation License, Index, BFD back ends, Top