Lines Matching refs:information

7 As different information from the object files is required,
21 * BFD information loss::	Information Loss
25 @node BFD information loss
30 information which can be described in one form has nowhere to go in
31 another format. One example of this is alignment information in
33 alignment information on the contained data, so when a file is linked
35 information will not propagate to the output file. (The linker will
36 still use the alignment information internally, so the link is performed
60 same time, the back end saves away any information which may otherwise
63 BFD core as well as the information it prepared earlier.  Since
65 there is no information lost when
67 @code{b.out}.  When a mixture of formats is linked, the information is
73 The greatest potential for loss of information occurs when there is the least
74 overlap between the information provided by the source format, that
96 information, various flags, and pointers into other BFD data
100 Each symbol contains a pointer to the information for the object file
114 information is not worth retaining; in @code{a.out}, type information is
115 stored in the symbol table as long symbol names.  This information would
119 There is one word of type information within the symbol, so if the
120 format supports symbol type information within symbols (for example, COFF,
122 (nearly everything but aggregates), the information will be preserved.
140 These addresses have to be relocated along with the symbol information.
146 which can simply derive this information can pass it successfully