Lines Matching refs:files
56 * BFD generated files:: BFD generated files
68 object files, executables, archive files, and core files in any format.
134 The third use is to link object files. There is only one object file
142 structures, in the normal case where all the input files and output file
157 into the generic form when reading files, and out of the generic form
158 when writing files.
193 Archive files do not have any sections or symbols. Instead, BFD
229 with object files, and particular problems caused by information loss
276 together the files for all targets.
281 which may or may not be declared in system header files. Warnings about
606 with core files. Obviously, these functions only do something
628 with archive files. Most targets use COFF style archive files
887 input files have been read, when it is ready to finish the link and
932 @node BFD generated files
933 @section BFD generated files
934 @cindex generated files in bfd
935 @cindex bfd generated files
937 BFD contains several automatically generated files. This section
938 describes them. Some files are created at configure time, when you
939 configure BFD. Some files are created at make time, when you build
940 BFD. Some files are automatically rebuilt at make time, but only if
942 files live in the object directory---the directory from which you run
943 configure---and some live in the source directory. All files that live
964 other BFD source files. If you configure with the
973 These files are versions of @file{elfxx-target.h} customized for either
979 several other BFD source files. If you configure with the
999 Several files in BFD are compiled multiple times. By this I mean that
1000 there are header files which contain function definitions. These header
1001 files are included by other files, and thus the functions are compiled
1005 time the files are compiled the resulting functions are slightly
1032 The following is a list of the files which are compiled multiple times.
1043 Implements standard SunOS a.out files. In principle it supports 64 bit
1046 work. This file is only included by a few other files, and it is
1074 definitions in the files in the @file{include/coff} directory. A COFF
1075 target file will include one of those files before including
1083 for ECOFF. It is included by the ECOFF target files (of which there are
1090 file is included by two other files: @file{elf32.c} and @file{elf64.c}.
1099 files. This is included only by @file{elfcode.h}.
1103 This file is the source for the generated files @file{elf32-target.h}
1116 Like @file{freebsd.h}, except that there are several files which include
1243 files and the output file, does not convert relocations into
1319 Linking input files of different object file formats together is quite
1403 a single file. The generic support is provided by several other files.
1411 * BFD ELF core files:: BFD ELF core files
1419 Relocatable object files conventionally have only sections.
1420 Executables conventionally have both. Core files conventionally have
1518 among these files and the processor specific files.
1523 The processor specific files may override particular entries in the
1585 files (but not in executables, except when using dynamic linking).
1708 @node BFD ELF core files
1709 @subsection BFD ELF core files
1710 @cindex elf core files
1712 On native ELF Unix systems, core files are generated without any
1732 ELF core files store special information such as register values in
1740 general, BFD does not provide a way to create core files. The way to
1785 A collection of object files produced and manipulated by the @samp{ar}
1839 The format of an object file. Typically object files and executables
1845 Windows (specifically, Win32) object files. It is based closely on
1858 Object files and executable are composed of sections. Sections have