Lines Matching refs:information

48 This document describes some BFD internal information which may be
78 * BFD blindness::		BFD loses information
134 information.  The official BFD interface includes functions to copy
135 private information from one object file to another, and these functions
136 are used by @samp{objcopy} to avoid information loss.
160 BFD uses generic structures to manage information.  It translates data
165 is composed of the following elements.  The BFD information can be
169 @item general information
185 information.
191 relocation.  For more information, see @ref{BFD relocation handling}.
205 @subsection BFD loses information
207 Most object file formats have information which BFD can not represent in
210 There is often explicit information which BFD can not represent.  For
212 provides special hooks to handle this information when copying,
214 object file format will normally store this information in private data
217 In some cases there is also implicit information which BFD can not
223 represent this information, this means that the assembler and linker
224 must have information that is specific to a particular object file
227 This loss of information indicates areas where the BFD paradigm breaks
233 with object files, and particular problems caused by information loss
314 * BFD target vector dynamic::		Dynamic linking information functions
376 The byte order of header information in the object file.  Normally the
404 whatever additional information they need to distinguish similar target
411 Every target vector has function pointers used for swapping information
413 functions: one for data information, and one for header information.
445 format specific information such as the @samp{tdata} field of the BFD.
453 specific information required to write out an object file or whatever of
461 @samp{bfd_set_format} function provides all the required information.
508 Free any target specific information associated with the BFD.  This is
512 information, and therefore don't have to do anything in this function.
517 Free any cached information associated with the BFD which can be
528 information.  This function is called whether or not the section
556 internal BFD information.
562 private information over.  This is called after all the section contents
582 store extra symbol information by allocating space which is larger than
583 the @samp{asymbol} structure and storing private information in the
585 information by copying pointers to @samp{asymbol} structures, the
586 private symbol information is automatically copied as well.  Most
591 for the assembler to set magic information.  For example, the PowerPC
598 information about the BFD which can not be otherwise represented by BFD
694 Do a stat on an element of an archive, returning information read from
720 information in BFD private data.  This is called via
731 store extra information with each symbol by allocating a structure
732 larger than an @samp{asymbol} and storing the extra information at the
739 Print information about the symbol.  This is called via
741 information should be printed:
750 Print all information about the symbol.  This is used by @samp{objdump}
757 Return a standard set of information about the symbol.  This is called
769 Return line number information for a symbol.  This is only meaningful
773 Given an address within a section, use the debugging information to find
787 information which the caller can use to extract complete symbol
788 information.  This permits BFD to not convert all the symbols into
812 store the actual relocation information in BFD private data.  This is
816 Return the relocation information for a section.  This is called via
856 Return the size of the header information required for a BFD.  This is
864 Read the contents of a section and apply the relocation information.
866 case, it adjust the relocation information as well.  This is called via
878 permits the backend to control the size and information of the elements
898 @subsection Dynamic linking information functions
902 dynamic linking information.
910 symbol information in BFD private data.  This is called via
924 actual relocation information in BFD private data.  This is called via
1427 information.  ELF relocations are stored in sections of a particular
1429 information.
1435 it.  The loader will ignore the section information.  Loadable program
1438 dynamic linking information.
1479 created automatically based on the section information.  This is done in
1632 information which may be needed outside of the BFD code.  In particular
1665 information, and modify the section contents according to the relocation
1666 information.  In simple cases, this is little more than a loop over the
1734 ELF core files store special information such as register values in
1736 interpret the information in these segments, and will create additional
1737 sections holding the information.  Some of this interpretation requires
1738 information found in the host header file @file{sys/procfs.h}, and so
1825 information.  Normally produced by a linker.
1838 information.  Normally produced by an assembler.
1843 will not contain any relocation information.
1853 to PE, but includes some additional header information.
1861 optional data and optional relocation information.
1872 address.  There may also be some additional information like the type of