Lines Matching refs:specific

85 directly or indirectly into calls to routines which are specific to a
92 of function pointers specific to a particular object file format.  The
100 specific to a particular object file format, are not generic functions,
140 The official BFD linker functions were written to permit specific BFD
169 etc.) and a specific machine number (m68000, R4000, etc.).
220 must have information that is specific to a particular object file
264 specific linker emulations.
292 behaviour that is specific to a particular object file format.
443 format specific information such as the @samp{tdata} field of the BFD.
451 specific information required to write out an object file or whatever of
506 Free any target specific information associated with the BFD.  This is
509 targets use @samp{bfd_alloc} to allocate all target specific
525 section is created.  Most targets use it to initialize section specific
1098 Like @file{elfcode.h}, but for functions that are specific to ELF core
1140 PE target.  This defines PE specific versions of the COFF swapping
1204 type field.  The type field is specific to the object file format
1247 handle relocations in a target specific fashion.
1249 There are two helper functions for target specific relocation:
1253 from target specific code, the @samp{special_function} field adds
1291 required handling to the target specific relocation function.  In simple
1332 enumeration.  The enumeration contains many target specific relocations,
1349 confusing.  There are many processor specific relocation codes.
1381 section functions used by the new linker.  The target specific code
1383 conversion) to convert target specific relocations into howto
1392 be given to writing ELF specific but ELF target generic code to handle
1401 processor specific supplement.  The ELF support in BFD is split in a
1402 similar fashion.  The processor specific support is largely kept within
1404 The processor specific support provides a set of function pointers and
1410 * BFD ELF processor specific support::	BFD ELF processor specific support
1506 linker support is only used if the processor specific file defines
1518 among these files and the processor specific files.
1523 The processor specific files may override particular entries in the
1525 @samp{bfd_reloc_type_lookup} entry point is always processor specific.
1527 @node BFD ELF processor specific support
1528 @subsection BFD ELF processor specific support
1530 By convention, the processor specific support for a particular processor
1535 * BFD ELF processor required::	Required processor specific support
1536 * BFD ELF processor linker::	Processor specific linker support
1537 * BFD ELF processor other::	Other processor specific support options
1541 @subsubsection Required processor specific support
1575 processor specific supplement.  For a processor which will only be used
1581 processor specific supplement.
1629 called @file{@var{cpu}.h}.  This file should define any target specific 
1641 @subsubsection Processor specific linker support
1644 function.  This will permit BFD to use the ELF specific linker support.
1678 @subsubsection Other processor specific support options
1687 Several processor specific hook functions which may be defined as
1693 There are a few processor specific constants which may also be defined.
1705 Dynamic linking support, which involves processor specific relocations
1759 handling.  Many of the COFF processor specific backends share a single
1764 The appearance of the processor specific magic number in