Lines Matching full:coff
56 object files in many different formats--for example, COFF or `a.out'.
476 text section is allowed for PE-COFF targets, it does not conform
1132 files for downloading into certain real time kernels with the COFF
1133 object file format; since COFF cannot represent more than 65535
1289 a few object file formats. For formats like COFF or ELF, the
1516 COFF header is set to indicate that this executable supports
1597 PE-COFF format specification published by Microsoft.
2910 For object file formats such as `COFF' or `ELF' which support
4205 * TI COFF:: `ld' and TI COFF
4493 File: ld.info, Node: PowerPC64 ELF64, Next: TI COFF, Prev: PowerPC ELF32, Up: Machine Dependent
4578 File: ld.info, Node: TI COFF, Next: WIN32, Prev: PowerPC64 ELF64, Up: Machine Dependent
4580 4.9 `ld''s Support for Various TI COFF Versions
4583 The `--format' switch allows selection of one of the various TI COFF
4585 supported. The TI COFF versions also vary in header byte-order format;
4590 File: ld.info, Node: WIN32, Next: Xtensa, Prev: TI COFF, Up: Machine Dependent
5131 Another example is COFF section names. COFF files may contain an
5157 linking or copying big endian COFF to little endian COFF, or `a.out' to
5207 This information would be useless to most COFF debuggers; the
5212 example, COFF, IEEE, Oasys) and the type is simple enough to fit
5227 byte being written to a 68k COFF file, even though 68k COFF has no
5241 formats (COFF, IEEE and Oasys).
5511 3. COFF (the `coff-m68k' variant in BFD), if OUTPUT-FORMAT is
5512 `COFF'
5991 * --format=VERSION: TI COFF. (line 6)
6578 * TI COFF versions: TI COFF. (line 6)
6677 Node: TI COFF193194
