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).
377 COFF header). */
386 /* BFD has local symbols (basically used for F_LSYMS in a COFF
1253 Names need not be unique; for example a COFF file may have several
1505 /* The section is a COFF shared library section. This flag is
1509 was originally intended to be general, it really is COFF
1517 executables or shared objects. This is for COFF only. */
1604 reloc contents (stabs, eh_frame, SEC_MERGE, some coff relaxing
2161 end knows about. For example, the coff back end keeps the original
2163 read in. On output, the coff back end can reconstruct the output symbol
2164 table so that no information is lost, even information unique to coff
2165 which BFD doesn't know or understand. If a coff symbol table were read,
2166 but were written through an a.out back end, all the coff specific
2368 location in an output file - ie in coff a `ISFCN' symbol
2622 different formats (e.g., a.out and coff) and even different
2626 more expressive than others. For instance, Intel COFF archives can
2827 generated only when linking i960 coff files with i960 b.out
2905 Using coff and an 88k, some instructions don't have enough space in
3004 in a coff environment has the type 023 - because that's
3178 record. Some native formats (e.g., basic a.out and basic coff) have no
5783 when creating COFF files. */
7755 * coff :: coff backends
7768 File: bfd.info, Node: aout, Next: coff, Prev: What to Put Where, Up: BFD back ends
7955 File: bfd.info, Node: coff, Next: elf, Prev: aout, Up: BFD back ends
7957 3.3 coff backends
7960 BFD supports a number of different flavours of coff format. The major
7964 Coff in all its varieties is implemented with a few common files and
7966 coff format is implemented in the file `coff-m88k.c'. This file
7967 `#include's `coff/m88k.h' which defines the external structure of the
7968 coff format for the 88k, and `coff/internal.h' which defines the
7969 internal structure. `coff-m88k.c' also defines the relocations used by
7972 The Intel i960 processor version of coff is implemented in
7973 `coff-i960.c'. This file has the same structure as `coff-m88k.c',
7974 except that it includes `coff/i960.h' rather than `coff-m88k.h'.
7976 3.3.1 Porting to a new version of coff
7980 the version of coff which is most like the one you want to use. For
7981 example, we'll say that i386 coff is the one you select, and that your
7982 coff flavour is called foo. Copy `i386coff.c' to `foocoff.c', copy
7983 `../include/coff/i386.h' to `../include/coff/foo.h', and add the lines
7985 Alter the shapes of the structures in `../include/coff/foo.h' so that
7987 to the code in `coff/internal.h' and `coffcode.h' if your version of
7988 coff is too wild.
7993 has the pretty standard coff dump utility, usually called `att-dump' or
7998 3.3.2 How the coff backend works
8004 The Coff backend is split into generic routines that are applicable to
8005 any Coff target and routines that are specific to a particular target.
8007 basically the same for all Coff
8011 any Coff target. They use some hooks into the target specific code;
8017 various Coff targets first include the appropriate Coff header file,
8020 Some of the Coff targets then also have additional routines in the
8023 For example, `coff-i960.c' includes `coff/internal.h' and
8024 `coff/i960.h'. It then defines a few constants, such as `I960', and
8026 `coff-i960.c' also includes some code to manipulate the i960 relocs.
8033 Each flavour of coff supported in BFD has its own header file
8035 internal description of the coff layout, in `coff/internal.h'. A major
8036 function of the coff backend is swapping the bytes and twiddling the
8040 of coff; it is the duty of the coff version specific include file to
8042 E.g., the size of line number entry in coff is sometimes 16 bits, and
8045 version of coff which has a varying field size not catered to at the
8064 keep all the information available in a coff symbol table. The back end
8070 `coff_get_normalized_symtab'. This reads the symbol table from the coff
8083 At this time the symbol names are moved around. Coff stores all
8095 Any linenumbers are read from the coff file too, and attached to the
8101 Writing a symbol to a coff file which didn't come from a coff file will
8106 When the symbols have come from a coff file then all the debugging
8120 form of BFD into the form used by coff. Internally, BFD expects symbol
8123 Coff expects symbols to contain their final value, so symbols have
8132 required by coff. It changes each pointer to a symbol into the index
8137 symbols from their internal form into the coff way, calls the bit
8204 /* COFF symbol classifications. */
8219 Special entry points for gdb to swap in coff symbol table parts:
8502 Creating the linenumber table is done by reading in the entire coff
8505 A coff linenumber table is structured so that each function is
8522 Coff relocations are easily transformed into the internal BFD form
8525 Reading a coff relocation table is done in the following stages:
8527 * Read the entire coff relocation table into memory.
8545 File: bfd.info, Node: elf, Next: mmo, Prev: coff, Up: BFD back ends
9371 * bfd_coff_backend_data: coff. (line 246)
10733 * coff_symbol_type: coff. (line 186)
10813 Node: coff292340
