Lines Matching refs:functions
83 The first interface is the set of generic functions which programs using
86 particular object file format. Many of these generic functions are
87 actually defined as macros in @file{bfd.h}. These functions comprise
90 The second interface is the set of functions which appear in the target
93 target vector is used to implement the generic BFD functions. These
94 functions are always called through the target vector, and are never
96 target vector}. The set of functions which appear in a particular
99 The third interface is a set of oddball functions which are typically
100 specific to a particular object file format, are not generic functions,
104 These functions are typically declared in @file{bfd.h}, but in many
106 particular object file format. These functions live in a grey area, and
109 The fourth interface is the set of BFD support functions which are
110 called by the other BFD functions. These manage issues like memory
112 like. These functions are never called from outside of the BFD library.
130 information. The official BFD interface includes functions to copy
131 private information from one object file to another, and these functions
140 The official BFD linker functions were written to permit specific BFD
144 implement the new interface, and there are default linking functions
150 linking support. These functions are typically called from the linker
260 All externally visible functions should have names which start with
261 @samp{bfd_}. All such functions should be declared in some header file,
263 the end of @file{bfd-in.h}, which mostly declare functions required by
267 All functions which need to be visible from one file to another within
299 * BFD target vector swap:: Swapping functions
300 * BFD target vector format:: Format type dependent functions
302 * BFD target vector generic:: Generic functions
303 * BFD target vector copy:: Copy functions
304 * BFD target vector core:: Core file support functions
305 * BFD target vector archive:: Archive functions
306 * BFD target vector symbols:: Symbol table functions
308 * BFD target vector write:: Output functions
309 * BFD target vector link:: Linker functions
310 * BFD target vector dynamic:: Dynamic linking information functions
403 vectors which use the same sets of functions.
407 @subsection Swapping functions
411 functions: one for data information, and one for header information.
413 three actual functions: put, get unsigned, and get signed.
415 These 18 functions are used to convert data between the host and target
419 @subsection Format type dependent functions
472 of functions. The macros are then used to initialize the fields in the
476 functions: @samp{_get_reloc_upper_bound}, @samp{_canonicalize_reloc},
478 @samp{BFD_JUMP_TABLE_RELOCS (foo)} will expand into three functions
481 functions initialize the appropriate fields in the BFD target vector.
484 share certain classes of functions. For example, archives are similar
486 functions. Those target vectors all use @samp{BFD_JUMP_TABLE_ARCHIVE}
487 with the same argument, calling a set of functions which is defined in
498 @subsection Generic functions
502 functions which don't easily fit into other categories.
549 @subsection Copy functions
552 The @samp{BFD_JUMP_TABLE_COPY} macro is used for functions which are
553 called when copying BFDs, and for a couple of functions which deal with
602 @subsection Core file support functions
605 The @samp{BFD_JUMP_TABLE_CORE} macro is used for functions which deal
606 with core files. Obviously, these functions only do something
624 @subsection Archive functions
627 The @samp{BFD_JUMP_TABLE_ARCHIVE} macro is used for functions which deal
706 @subsection Symbol table functions
709 The @samp{BFD_JUMP_TABLE_SYMBOLS} macro is used for functions which deal
801 The @samp{BFD_JUMP_TABLE_RELOCS} macro is used for functions which deal
826 @subsection Output functions
829 The @samp{BFD_JUMP_TABLE_WRITE} macro is used for functions which deal
846 @subsection Linker functions
849 The @samp{BFD_JUMP_TABLE_LINK} macro is used for functions called by the
896 @subsection Dynamic linking information functions
899 The @samp{BFD_JUMP_TABLE_DYNAMIC} macro is used for functions which read
1001 files are included by other files, and thus the functions are compiled
1005 time the files are compiled the resulting functions are slightly
1037 Describes a few functions and the target vector for a.out targets. This
1056 the functions it defined. Unfortunately, some other a.out targets
1064 well as various hook functions called by the generic COFF functions in
1089 Implements ELF functions that use external structure definitions. This
1093 used internally to give the functions different names for the two target
1098 Like @file{elfcode.h}, but for functions that are specific to ELF core
1156 * BFD relocation functions:: BFD relocation functions
1197 @node BFD relocation functions
1198 @subsection BFD relocation functions
1249 There are two helper functions for target specific relocation:
1251 These functions use a howto structure, but they @emph{do not} use the
1252 @samp{special_function} field. Since the functions are normally called
1255 without calling those functions.
1377 One or more generic functions similar to @samp{bfd_perform_relocation}
1381 section functions used by the new linker. The target specific code
1492 In general, functions which do not read external data from the ELF file
1498 The file @file{elfcode.h} contains functions which operate on the
1502 @file{elfcode.h} includes functions to swap the ELF structures in and
1503 out of external form, as well as a few more complex functions.
1521 @file{elf.c}. Some functions are found in @file{elfcode.h}.
1685 functions.
1687 Several processor specific hook functions which may be defined as
1688 macros. These functions are found as function pointers in the
1696 I will not define the various functions and constants here; see the
1706 requiring special handling, is also implemented via hook functions.
1753 generic functions, eliminating the duplication.
1756 the @samp{reloc_type_lookup} and @samp{info_to_howto} functions are
1757 quite similar. The relocate section functions are also often quite
1790 set of functions which appear in a particular target vector.
1862 A library of functions which may be used by many executables without
1877 A set of functions which implement support for a particular object file