Lines Matching full:coff
78 Intel Oregon, for interoperability of applications on their COFF and
88 coff.
138 coff, but loses efficiency when applied to formats such as S-records and
186 Another example is COFF section names. COFF files may contain an
212 linking or copying big endian COFF to little endian COFF, or `a.out' to
262 This information would be useless to most COFF debuggers; the
267 example, COFF, IEEE, Oasys) and the type is simple enough to fit
282 byte being written to a 68k COFF file, even though 68k COFF has no
296 formats (COFF, IEEE and Oasys).
378 COFF header). */
387 /* BFD has local symbols (basically used for F_LSYMS in a COFF
1273 Names need not be unique; for example a COFF file may have several
1525 /* The section is a COFF shared library section. This flag is
1529 was originally intended to be general, it really is COFF
1537 executables or shared objects. This is for COFF only. */
1623 reloc contents (stabs, eh_frame, SEC_MERGE, some coff relaxing
2198 end knows about. For example, the coff back end keeps the original
2200 read in. On output, the coff back end can reconstruct the output symbol
2201 table so that no information is lost, even information unique to coff
2202 which BFD doesn't know or understand. If a coff symbol table were read,
2203 but were written through an a.out back end, all the coff specific
2402 location in an output file - ie in coff a `ISFCN' symbol
2666 different formats (e.g., a.out and coff) and even different
2670 more expressive than others. For instance, Intel COFF archives can
2871 generated only when linking i960 coff files with i960 b.out
2949 Using coff and an 88k, some instructions don't have enough space in
3048 in a coff environment has the type 023 - because that's
3222 record. Some native formats (e.g., basic a.out and basic coff) have no
6017 when creating COFF files. */
8073 * coff :: coff backends
8086 File: bfd.info, Node: aout, Next: coff, Prev: What to Put Where, Up: BFD back ends
8273 File: bfd.info, Node: coff, Next: elf, Prev: aout, Up: BFD back ends
8275 3.3 coff backends
8278 BFD supports a number of different flavours of coff format. The major
8282 Coff in all its varieties is implemented with a few common files and
8284 coff format is implemented in the file `coff-m88k.c'. This file
8285 `#include's `coff/m88k.h' which defines the external structure of the
8286 coff format for the 88k, and `coff/internal.h' which defines the
8287 internal structure. `coff-m88k.c' also defines the relocations used by
8290 The Intel i960 processor version of coff is implemented in
8291 `coff-i960.c'. This file has the same structure as `coff-m88k.c',
8292 except that it includes `coff/i960.h' rather than `coff-m88k.h'.
8294 3.3.1 Porting to a new version of coff
8298 the version of coff which is most like the one you want to use. For
8299 example, we'll say that i386 coff is the one you select, and that your
8300 coff flavour is called foo. Copy `i386coff.c' to `foocoff.c', copy
8301 `../include/coff/i386.h' to `../include/coff/foo.h', and add the lines
8303 Alter the shapes of the structures in `../include/coff/foo.h' so that
8305 to the code in `coff/internal.h' and `coffcode.h' if your version of
8306 coff is too wild.
8311 has the pretty standard coff dump utility, usually called `att-dump' or
8316 3.3.2 How the coff backend works
8322 The Coff backend is split into generic routines that are applicable to
8323 any Coff target and routines that are specific to a particular target.
8325 basically the same for all Coff targets except that they use the
8329 any Coff target. They use some hooks into the target specific code;
8335 various Coff targets first include the appropriate Coff header file,
8338 Some of the Coff targets then also have additional routines in the
8341 For example, `coff-i960.c' includes `coff/internal.h' and
8342 `coff/i960.h'. It then defines a few constants, such as `I960', and
8344 `coff-i960.c' also includes some code to manipulate the i960 relocs.
8348 3.3.2.2 Coff long section names
8351 In the standard Coff object format, section names are limited to the
8357 The Microsoft PE variants of the Coff object file format add an
8359 defined in section 4 of the Microsoft PE/COFF specification (rev 8.1).
8373 technically valid, as the standard only says that Coff debugging
8382 hook function pointer, `_bfd_coff_set_long_section_names', in the Coff
8409 Each flavour of coff supported in BFD has its own header file
8411 internal description of the coff layout, in `coff/internal.h'. A major
8412 function of the coff backend is swapping the bytes and twiddling the
8416 of coff; it is the duty of the coff version specific include file to
8418 E.g., the size of line number entry in coff is sometimes 16 bits, and
8421 version of coff which has a varying field size not catered to at the
8440 keep all the information available in a coff symbol table. The back end
8446 `coff_get_normalized_symtab'. This reads the symbol table from the coff
8459 At this time the symbol names are moved around. Coff stores all
8471 Any linenumbers are read from the coff file too, and attached to the
8477 Writing a symbol to a coff file which didn't come from a coff file will
8482 When the symbols have come from a coff file then all the debugging
8496 form of BFD into the form used by coff. Internally, BFD expects symbol
8499 Coff expects symbols to contain their final value, so symbols have
8508 required by coff. It changes each pointer to a symbol into the index
8513 symbols from their internal form into the coff way, calls the bit
8580 /* COFF symbol classifications. */
8595 Special entry points for gdb to swap in coff symbol table parts:
8889 Creating the linenumber table is done by reading in the entire coff
8892 A coff linenumber table is structured so that each function is
8909 Coff relocations are easily transformed into the internal BFD form
8912 Reading a coff relocation table is done in the following stages:
8914 * Read the entire coff relocation table into memory.
8932 File: bfd.info, Node: elf, Next: mmo, Prev: coff, Up: BFD back ends
9855 * bfd_coff_backend_data: coff. (line 304)
11322 * coff_symbol_type: coff. (line 244)
11402 Node: coff304377
