Lines Matching full:coff
79 Intel Oregon, for interoperability of applications on their COFF and
89 coff.
139 coff, but loses efficiency when applied to formats such as S-records and
187 Another example is COFF section names. COFF files may contain an
213 linking or copying big endian COFF to little endian COFF, or `a.out' to
263 This information would be useless to most COFF debuggers; the
268 example, COFF, IEEE, Oasys) and the type is simple enough to fit
283 byte being written to a 68k COFF file, even though 68k COFF has no
297 formats (COFF, IEEE and Oasys).
378 COFF header). */
387 /* BFD has local symbols (basically used for F_LSYMS in a COFF
1254 Names need not be unique; for example a COFF file may have several
1506 /* The section is a COFF shared library section. This flag is
1510 was originally intended to be general, it really is COFF
1518 executables or shared objects. This is for COFF only. */
1605 reloc contents (stabs, eh_frame, SEC_MERGE, some coff relaxing
2162 end knows about. For example, the coff back end keeps the original
2164 read in. On output, the coff back end can reconstruct the output symbol
2165 table so that no information is lost, even information unique to coff
2166 which BFD doesn't know or understand. If a coff symbol table were read,
2167 but were written through an a.out back end, all the coff specific
2369 location in an output file - ie in coff a `ISFCN' symbol
2623 different formats (e.g., a.out and coff) and even different
2627 more expressive than others. For instance, Intel COFF archives can
2828 generated only when linking i960 coff files with i960 b.out
2906 Using coff and an 88k, some instructions don't have enough space in
3005 in a coff environment has the type 023 - because that's
3179 record. Some native formats (e.g., basic a.out and basic coff) have no
5784 when creating COFF files. */
7756 * coff :: coff backends
7769 File: bfd.info, Node: aout, Next: coff, Prev: What to Put Where, Up: BFD back ends
7956 File: bfd.info, Node: coff, Next: elf, Prev: aout, Up: BFD back ends
7958 3.3 coff backends
7961 BFD supports a number of different flavours of coff format. The major
7965 Coff in all its varieties is implemented with a few common files and
7967 coff format is implemented in the file `coff-m88k.c'. This file
7968 `#include's `coff/m88k.h' which defines the external structure of the
7969 coff format for the 88k, and `coff/internal.h' which defines the
7970 internal structure. `coff-m88k.c' also defines the relocations used by
7973 The Intel i960 processor version of coff is implemented in
7974 `coff-i960.c'. This file has the same structure as `coff-m88k.c',
7975 except that it includes `coff/i960.h' rather than `coff-m88k.h'.
7977 3.3.1 Porting to a new version of coff
7981 the version of coff which is most like the one you want to use. For
7982 example, we'll say that i386 coff is the one you select, and that your
7983 coff flavour is called foo. Copy `i386coff.c' to `foocoff.c', copy
7984 `../include/coff/i386.h' to `../include/coff/foo.h', and add the lines
7986 Alter the shapes of the structures in `../include/coff/foo.h' so that
7988 to the code in `coff/internal.h' and `coffcode.h' if your version of
7989 coff is too wild.
7994 has the pretty standard coff dump utility, usually called `att-dump' or
7999 3.3.2 How the coff backend works
8005 The Coff backend is split into generic routines that are applicable to
8006 any Coff target and routines that are specific to a particular target.
8008 basically the same for all Coff
8012 any Coff target. They use some hooks into the target specific code;
8018 various Coff targets first include the appropriate Coff header file,
8021 Some of the Coff targets then also have additional routines in the
8024 For example, `coff-i960.c' includes `coff/internal.h' and
8025 `coff/i960.h'. It then defines a few constants, such as `I960', and
8027 `coff-i960.c' also includes some code to manipulate the i960 relocs.
8034 Each flavour of coff supported in BFD has its own header file
8036 internal description of the coff layout, in `coff/internal.h'. A major
8037 function of the coff backend is swapping the bytes and twiddling the
8041 of coff; it is the duty of the coff version specific include file to
8043 E.g., the size of line number entry in coff is sometimes 16 bits, and
8046 version of coff which has a varying field size not catered to at the
8065 keep all the information available in a coff symbol table. The back end
8071 `coff_get_normalized_symtab'. This reads the symbol table from the coff
8084 At this time the symbol names are moved around. Coff stores all
8096 Any linenumbers are read from the coff file too, and attached to the
8102 Writing a symbol to a coff file which didn't come from a coff file will
8107 When the symbols have come from a coff file then all the debugging
8121 form of BFD into the form used by coff. Internally, BFD expects symbol
8124 Coff expects symbols to contain their final value, so symbols have
8133 required by coff. It changes each pointer to a symbol into the index
8138 symbols from their internal form into the coff way, calls the bit
8205 /* COFF symbol classifications. */
8220 Special entry points for gdb to swap in coff symbol table parts:
8503 Creating the linenumber table is done by reading in the entire coff
8506 A coff linenumber table is structured so that each function is
8523 Coff relocations are easily transformed into the internal BFD form
8526 Reading a coff relocation table is done in the following stages:
8528 * Read the entire coff relocation table into memory.
8546 File: bfd.info, Node: elf, Next: mmo, Prev: coff, Up: BFD back ends
9373 * bfd_coff_backend_data: coff. (line 246)
10735 * coff_symbol_type: coff. (line 186)
10815 Node: coff292334
