Lines Matching full:coff
63 object files in many different formats--for example, COFF or `a.out'.
488 text section is allowed for PE-COFF targets, it does not conform
1239 files for downloading into certain real time kernels with the COFF
1240 object file format; since COFF cannot represent more than 65535
1396 a few object file formats. For formats like COFF or ELF, the
1650 the COFF header is set to indicate that this executable supports
1731 PE-COFF format specification published by Microsoft.
3132 For object file formats such as `COFF' or `ELF' which support
4463 * TI COFF:: `ld' and TI COFF
4993 File: ld.info, Node: SPU ELF, Next: TI COFF, Prev: PowerPC64 ELF64, Up: Machine Dependent
5049 File: ld.info, Node: TI COFF, Next: WIN32, Prev: SPU ELF, Up: Machine Dependent
5051 4.12 `ld''s Support for Various TI COFF Versions
5054 The `--format' switch allows selection of one of the various TI COFF
5056 supported. The TI COFF versions also vary in header byte-order format;
5061 File: ld.info, Node: WIN32, Next: Xtensa, Prev: TI COFF, Up: Machine Dependent
5608 Another example is COFF section names. COFF files may contain an
5634 linking or copying big endian COFF to little endian COFF, or `a.out' to
5684 This information would be useless to most COFF debuggers; the
5689 example, COFF, IEEE, Oasys) and the type is simple enough to fit
5704 byte being written to a 68k COFF file, even though 68k COFF has no
5718 formats (COFF, IEEE and Oasys).
5989 3. COFF (the `coff-m68k' variant in BFD), if OUTPUT-FORMAT is
5990 `COFF'
6482 * --format=VERSION: TI COFF. (line 6)
7111 * TI COFF versions: TI COFF. (line 6)
7216 Node: TI COFF215283
