Lines Matching full:coff
62 object files in many different formats--for example, COFF or `a.out'.
487 text section is allowed for PE-COFF targets, it does not conform
1238 files for downloading into certain real time kernels with the COFF
1239 object file format; since COFF cannot represent more than 65535
1395 a few object file formats. For formats like COFF or ELF, the
1649 the COFF header is set to indicate that this executable supports
1730 PE-COFF format specification published by Microsoft.
3131 For object file formats such as `COFF' or `ELF' which support
4462 * TI COFF:: `ld' and TI COFF
4983 File: ld.info, Node: SPU ELF, Next: TI COFF, Prev: PowerPC64 ELF64, Up: Machine Dependent
5039 File: ld.info, Node: TI COFF, Next: WIN32, Prev: SPU ELF, Up: Machine Dependent
5041 4.12 `ld''s Support for Various TI COFF Versions
5044 The `--format' switch allows selection of one of the various TI COFF
5046 supported. The TI COFF versions also vary in header byte-order format;
5051 File: ld.info, Node: WIN32, Next: Xtensa, Prev: TI COFF, Up: Machine Dependent
5598 Another example is COFF section names. COFF files may contain an
5624 linking or copying big endian COFF to little endian COFF, or `a.out' to
5674 This information would be useless to most COFF debuggers; the
5679 example, COFF, IEEE, Oasys) and the type is simple enough to fit
5694 byte being written to a 68k COFF file, even though 68k COFF has no
5708 formats (COFF, IEEE and Oasys).
5979 3. COFF (the `coff-m68k' variant in BFD), if OUTPUT-FORMAT is
5980 `COFF'
6471 * --format=VERSION: TI COFF. (line 6)
7098 * TI COFF versions: TI COFF. (line 6)
7203 Node: TI COFF214797
