Lines Matching refs:used
93 target vector is used to implement the generic BFD functions. These
101 and are called from outside of the BFD library. These are used as hooks
118 by the manner in which it is used.
132 are used by @samp{objcopy} to avoid information loss.
254 that it can be used in multiple threads. All uses of global or static
352 SOM (used on HP/UX).
370 @samp{BFD_ENDIAN_UNKNOWN}. The latter would be used for a format such
401 A pointer to constant backend data. This is used by backends to store
409 Every target vector has function pointers used for swapping information
415 These 18 functions are used to convert data between the host and target
426 Unknown format. Not used for anything useful.
460 In fact, BFD will fail if a different format is used when calling
472 of functions. The macros are then used to initialize the fields in the
501 The @samp{BFD_JUMP_TABLE_GENERIC} macro is used for some catch all
516 recreated later if necessary. This is used to reduce the memory
518 the @samp{bfd_free_cached_info} macro. It is used by the default
552 The @samp{BFD_JUMP_TABLE_COPY} macro is used for functions which are
578 think anything actually calls it. If it were defined, it could be used
594 This is called by @samp{objdump} when the @samp{-p} option is used. It
605 The @samp{BFD_JUMP_TABLE_CORE} macro is used for functions which deal
627 The @samp{BFD_JUMP_TABLE_ARCHIVE} macro is used for functions which deal
709 The @samp{BFD_JUMP_TABLE_SYMBOLS} macro is used for functions which deal
748 Print all information about the symbol. This is used by @samp{objdump}
783 Minisymbols are used to reduce the memory requirements of programs like
801 The @samp{BFD_JUMP_TABLE_RELOCS} macro is used for functions which deal
829 The @samp{BFD_JUMP_TABLE_WRITE} macro is used for functions which deal
849 The @samp{BFD_JUMP_TABLE_LINK} macro is used for functions called by the
855 used to implement the @samp{SIZEOF_HEADERS} linker script function. It
856 is normally used to align the first section at an efficient position on
870 by the linker when the @samp{-relax} option is used. This is called via
899 The @samp{BFD_JUMP_TABLE_DYNAMIC} macro is used for functions which read
993 @file{config.bfd}. This file is used to map configuration triplets into
1004 Preprocessor macros are used to control the compilation, so that each
1014 Since this technique is rarely used, even experienced C programmers find
1038 is used by individual a.out targets with different definitions of
1093 used internally to give the functions different names for the two target
1111 function used to set the right magic number for FreeBSD, as well as
1187 relocations used in dynamic linking systems often require the linker to
1220 S-records). The generic linker code, which is used by all targets which
1225 is still widely used, which makes it difficult to change, since it is
1228 The assembler used @samp{bfd_perform_relocation} for a while. This
1334 used. For example, the single value @samp{BFD_RELOC_32} is used for all
1346 relocation code. This is mainly used in error messages.
1357 be used for a particular target. It might be possible to replace the
1369 howto structure. Some mechanism would be used to determine which type
1370 of howto structure was being used by a particular format.
1381 section functions used by the new linker. The target specific code
1389 currently normally used.
1405 constants used by the generic support.
1450 offset in the file as in memory, modulo the memory page size used on the
1462 way to examine both sections and segments. When BFD is used to open an
1464 When BFD is used to open a core file, the BFD sections will represent
1467 When BFD is used to examine an object file or executable, any program
1476 When BFD is used to create an executable, the program segments will be
1482 There is a hook which may be used to explicitly define the program
1496 be used for both 32 bit and 64 bit ELF targets.
1506 linker support is only used if the processor specific file defines
1509 is used, and relocations are handled via @samp{bfd_perform_relocation}.
1517 The BFD internal header file @file{elf-bfd.h} is used for communication
1557 both, to a string used as the name of the target vector. This is the
1575 processor specific supplement. For a processor which will only be used
1633 macros to create a table mapping the number used to identify a
1684 Macros may be used to override some of the generic ELF target vector
1715 When BFD is used to read an ELF core file, the BFD sections will
1782 Still used on SunOS, though not Solaris. Supports only three sections.
1817 The Executable and Linking Format. The object file format used on most
1819 used on many embedded systems.
1844 The Portable Executable format. This is the object file format used for
1850 used for Windows (specifically, Win32) executables. It is very similar
1854 Information used by the linker to adjust section contents. Also called
1862 A library of functions which may be used by many executables without