Lines Matching full:coff
68 Intel Oregon, for interoperability of applications on their COFF and
78 coff.
128 coff, but loses efficiency when applied to formats such as S-records and
176 Another example is COFF section names. COFF files may contain an
202 linking or copying big endian COFF to little endian COFF, or `a.out' to
252 This information would be useless to most COFF debuggers; the
257 example, COFF, IEEE, Oasys) and the type is simple enough to fit
272 byte being written to a 68k COFF file, even though 68k COFF has no
286 formats (COFF, IEEE and Oasys).
1153 Names need not be unique; for example a COFF file may have several
1405 /* The section is a COFF shared library section. This flag is
1409 was originally intended to be general, it really is COFF
1417 executables or shared objects. This is for COFF only. */
1505 SEC_MERGE, some coff relaxing targets), and thus the original size
2062 end knows about. For example, the coff back end keeps the original
2064 read in. On output, the coff back end can reconstruct the output symbol
2065 table so that no information is lost, even information unique to coff
2066 which BFD doesn't know or understand. If a coff symbol table were read,
2067 but were written through an a.out back end, all the coff specific
2269 location in an output file - ie in coff a `ISFCN' symbol
2512 different formats (e.g., a.out and coff) and even different
2516 more expressive than others. For instance, Intel COFF archives can
2717 generated only when linking i960 coff files with i960 b.out
2795 Using coff and an 88k, some instructions don't have enough space in
2894 in a coff environment has the type 023 - because that's
3068 record. Some native formats (e.g., basic a.out and basic coff) have no
5581 when creating COFF files. */
7522 * coff :: coff backends
7535 File: bfd.info, Node: aout, Next: coff, Prev: What to Put Where, Up: BFD back ends
7722 File: bfd.info, Node: coff, Next: elf, Prev: aout, Up: BFD back ends
7724 3.3 coff backends
7727 BFD supports a number of different flavours of coff format. The major
7731 Coff in all its varieties is implemented with a few common files and
7733 coff format is implemented in the file `coff-m88k.c'. This file
7734 `#include's `coff/m88k.h' which defines the external structure of the
7735 coff format for the 88k, and `coff/internal.h' which defines the
7736 internal structure. `coff-m88k.c' also defines the relocations used by
7739 The Intel i960 processor version of coff is implemented in
7740 `coff-i960.c'. This file has the same structure as `coff-m88k.c',
7741 except that it includes `coff/i960.h' rather than `coff-m88k.h'.
7743 3.3.1 Porting to a new version of coff
7747 the version of coff which is most like the one you want to use. For
7748 example, we'll say that i386 coff is the one you select, and that your
7749 coff flavour is called foo. Copy `i386coff.c' to `foocoff.c', copy
7750 `../include/coff/i386.h' to `../include/coff/foo.h', and add the lines
7752 Alter the shapes of the structures in `../include/coff/foo.h' so that
7754 to the code in `coff/internal.h' and `coffcode.h' if your version of
7755 coff is too wild.
7760 has the pretty standard coff dump utility, usually called `att-dump' or
7765 3.3.2 How the coff backend works
7771 The Coff backend is split into generic routines that are applicable to
7772 any Coff target and routines that are specific to a particular target.
7774 basically the same for all Coff targets except that they use the
7778 any Coff target. They use some hooks into the target specific code;
7784 various Coff targets first include the appropriate Coff header file,
7787 Some of the Coff targets then also have additional routines in the
7790 For example, `coff-i960.c' includes `coff/internal.h' and
7791 `coff/i960.h'. It then defines a few constants, such as `I960', and
7793 `coff-i960.c' also includes some code to manipulate the i960 relocs.
7800 Each flavour of coff supported in BFD has its own header file
7802 internal description of the coff layout, in `coff/internal.h'. A major
7803 function of the coff backend is swapping the bytes and twiddling the
7807 of coff; it is the duty of the coff version specific include file to
7809 E.g., the size of line number entry in coff is sometimes 16 bits, and
7812 version of coff which has a varying field size not catered to at the
7831 keep all the information available in a coff symbol table. The back end
7837 `coff_get_normalized_symtab'. This reads the symbol table from the coff
7850 At this time the symbol names are moved around. Coff stores all
7862 Any linenumbers are read from the coff file too, and attached to the
7868 Writing a symbol to a coff file which didn't come from a coff file will
7873 When the symbols have come from a coff file then all the debugging
7887 form of BFD into the form used by coff. Internally, BFD expects symbol
7890 Coff expects symbols to contain their final value, so symbols have
7899 required by coff. It changes each pointer to a symbol into the index
7904 symbols from their internal form into the coff way, calls the bit
7971 /* COFF symbol classifications. */
7986 Special entry points for gdb to swap in coff symbol table parts:
8261 Creating the linenumber table is done by reading in the entire coff
8264 A coff linenumber table is structured so that each function is
8281 Coff relocations are easily transformed into the internal BFD form
8284 Reading a coff relocation table is done in the following stages:
8286 * Read the entire coff relocation table into memory.
8304 File: bfd.info, Node: elf, Next: mmo, Prev: coff, Up: BFD back ends
9131 * bfd_coff_backend_data: coff. (line 246)
10422 * coff_symbol_type: coff. (line 186)
10502 Node: coff284051
