Lines Matching full:coff
63 object files in many different formats--for example, COFF or `a.out'.
518 text section is allowed for PE-COFF targets, it does not conform
1285 files for downloading into certain real time kernels with the COFF
1286 object file format; since COFF cannot represent more than 65535
1450 a few object file formats. For formats like COFF or ELF, the
1632 The PE variants of the Coff object format add an extension that
1634 normal limit for Coff. By default, these names are only allowed
1636 the Coff string table required to support the longer names. As a
1729 the COFF header is set to indicate that this executable supports
1810 PE-COFF format specification published by Microsoft.
3389 For object file formats such as `COFF' or `ELF' which support
4774 * TI COFF:: `ld' and TI COFF
5312 File: ld.info, Node: SPU ELF, Next: TI COFF, Prev: PowerPC64 ELF64, Up: Machine Dependent
5368 File: ld.info, Node: TI COFF, Next: WIN32, Prev: SPU ELF, Up: Machine Dependent
5370 4.12 `ld''s Support for Various TI COFF Versions
5373 The `--format' switch allows selection of one of the various TI COFF
5375 supported. The TI COFF versions also vary in header byte-order format;
5380 File: ld.info, Node: WIN32, Next: Xtensa, Prev: TI COFF, Up: Machine Dependent
5953 Another example is COFF section names. COFF files may contain an
5979 linking or copying big endian COFF to little endian COFF, or `a.out' to
6029 This information would be useless to most COFF debuggers; the
6034 example, COFF, IEEE, Oasys) and the type is simple enough to fit
6049 byte being written to a 68k COFF file, even though 68k COFF has no
6063 formats (COFF, IEEE and Oasys).
6334 3. COFF (the `coff-m68k' variant in BFD), if OUTPUT-FORMAT is
6335 `COFF'
6832 * --format=VERSION: TI COFF. (line 6)
7489 * TI COFF versions: TI COFF. (line 6)
7597 Node: TI COFF227645
