Lines Matching full:information
9 As different information from the object files is required,
23 * BFD information loss:: Information Loss
27 @node BFD information loss
28 @subsection Information Loss
30 @emph{Information can be lost during output.} The output formats
32 information which can be described in one form has nowhere to go in
33 another format. One example of this is alignment information in
35 alignment information on the contained data, so when a file is linked
37 information will not propagate to the output file. (The linker will
38 still use the alignment information internally, so the link is performed
49 @emph{Information can be lost during canonicalization.} The BFD
62 same time, the back end saves away any information which may otherwise
65 BFD core as well as the information it prepared earlier. Since
67 there is no information lost when
69 @code{b.out}. When a mixture of formats is linked, the information is
75 The greatest potential for loss of information occurs when there is the least
76 overlap between the information provided by the source format, that
86 Information stored on a per-file basis includes target machine
88 bit, and a write protected bit. Information like Unix magic numbers is
98 information, various flags, and pointers into other BFD data
102 Each symbol contains a pointer to the information for the object file
116 information is not worth retaining; in @code{a.out}, type information is
117 stored in the symbol table as long symbol names. This information would
121 There is one word of type information within the symbol, so if the
122 format supports symbol type information within symbols (for example, COFF,
124 (nearly everything but aggregates), the information will be preserved.
142 These addresses have to be relocated along with the symbol information.
148 which can simply derive this information can pass it successfully
