Lines Matching +refs:dwarf +refs:file
5 @c For copying conditions, see the file gcc.texi.
36 @c Set file name and title for the man page.
46 [@option{-o} @var{outfile}] [@@@var{file}] @var{infile}@dots{}
54 and the Info entries for @file{gcc}, @file{cpp}, @file{as},
55 @file{ld}, @file{binutils} and @file{gdb}.
99 The @command{gcc} program accepts options and file names as operands. Many
165 @gccoptlist{-c -S -E -o @var{file} -no-canonical-prefixes @gol
168 --version -wrapper @@@var{file} -fplugin=@var{file} -fplugin-arg-@var{name}=@var{arg} @gol
169 -fdump-ada-spec@r{[}-slim@r{]} -fdump-go-spec=@var{file}}
323 -fdump-final-insns=@var{file} @gol
337 -gstabs -gstabs+ -gstrict-dwarf -gno-strict-dwarf @gol
343 -p -pg -print-file-name=@var{library} -print-libgcc-file-name @gol
347 -save-temps -save-temps=cwd -save-temps=obj -time@r{[}=@var{file}@r{]}}
429 -include @var{file} -imacros @var{file} @gol
430 -iprefix @var{file} -iwithprefix @var{dir} @gol
444 @gccoptlist{@var{object-file-name} -l@var{library} @gol
454 -iquote@var{dir} -L@var{dir} -specs=@var{file} -I- @gol
464 @gccoptlist{-mhalf-reg-file -mprefer-short-insn-regs @gol
539 -dependency-file -dylib_file -dylinker_install_name @gol
978 -finstrument-functions-exclude-file-list=@var{file},@var{file},@dots{} @gol
1022 assembler input files, or into one assembler input file; then each
1023 assembler input file produces an object file, and linking combines all
1025 into an executable file.
1027 @cindex file name suffix
1028 For any given input file, the file name suffix determines what kind of
1032 @item @var{file}.c
1035 @item @var{file}.i
1038 @item @var{file}.ii
1041 @item @var{file}.m
1042 Objective-C source code. Note that you must link with the @file{libobjc}
1045 @item @var{file}.mi
1048 @item @var{file}.mm
1049 @itemx @var{file}.M
1050 Objective-C++ source code. Note that you must link with the @file{libobjc}
1054 @item @var{file}.mii
1057 @item @var{file}.h
1058 C, C++, Objective-C or Objective-C++ header file to be turned into a
1059 precompiled header (default), or C, C++ header file to be turned into an
1062 @item @var{file}.cc
1063 @itemx @var{file}.cp
1064 @itemx @var{file}.cxx
1065 @itemx @var{file}.cpp
1066 @itemx @var{file}.CPP
1067 @itemx @var{file}.c++
1068 @itemx @var{file}.C
1073 @item @var{file}.mm
1074 @itemx @var{file}.M
1077 @item @var{file}.mii
1080 @item @var{file}.hh
1081 @itemx @var{file}.H
1082 @itemx @var{file}.hp
1083 @itemx @var{file}.hxx
1084 @itemx @var{file}.hpp
1085 @itemx @var{file}.HPP
1086 @itemx @var{file}.h++
1087 @itemx @var{file}.tcc
1088 C++ header file to be turned into a precompiled header or Ada spec.
1090 @item @var{file}.f
1091 @itemx @var{file}.for
1092 @itemx @var{file}.ftn
1095 @item @var{file}.F
1096 @itemx @var{file}.FOR
1097 @itemx @var{file}.fpp
1098 @itemx @var{file}.FPP
1099 @itemx @var{file}.FTN
1103 @item @var{file}.f90
1104 @itemx @var{file}.f95
1105 @itemx @var{file}.f03
1106 @itemx @var{file}.f08
1109 @item @var{file}.F90
1110 @itemx @var{file}.F95
1111 @itemx @var{file}.F03
1112 @itemx @var{file}.F08
1116 @item @var{file}.go
1119 @c FIXME: Descriptions of Java file types.
1120 @c @var{file}.java
1121 @c @var{file}.class
1122 @c @var{file}.zip
1123 @c @var{file}.jar
1125 @item @var{file}.ads
1126 Ada source code file that contains a library unit declaration (a
1132 @item @var{file}.adb
1133 Ada source code file containing a library unit body (a subprogram or
1138 @c @var{file}.p
1139 @c @var{file}.pas
1141 @c @var{file}.r
1143 @item @var{file}.s
1146 @item @var{file}.S
1147 @itemx @var{file}.sx
1151 An object file to be fed straight into linking.
1152 Any file name with no recognized suffix is treated this way.
1161 (rather than letting the compiler choose a default based on the file
1178 handled according to their file name suffixes (as they are if @option{-x}
1202 object file for each source file.
1204 By default, the object file name for a source file is made by replacing
1213 is in the form of an assembler code file for each non-assembler input
1214 file specified.
1216 By default, the assembler file name for a source file is made by
1229 @cindex output file option
1230 @item -o @var{file}
1232 Place output in file @var{file}. This applies regardless to whatever
1233 sort of output is being produced, whether it be an executable file,
1234 an object file, an assembler file or preprocessed C code.
1237 file in @file{a.out}, the object file for
1238 @file{@var{source}.@var{suffix}} in @file{@var{source}.o}, its
1239 assembler file in @file{@var{source}.s}, a precompiled header file in
1240 @file{@var{source}.@var{suffix}.gch}, and all preprocessed C source on
1324 following the original option, such as: @samp{-o output-file}.
1419 Load the plugin code in file @var{name}.so, assumed to be a
1421 the shared object file is used to identify the plugin for the
1437 @item -fdump-go-spec=@var{file}
1440 declarations in @var{file}. This generates Go @code{const},
1445 @include @value{srcdir}/../libiberty/at-file.texi
1452 @cindex C++ source file suffixes
1469 precompiling a C header file with a @samp{.h} extension for use in C++
1645 Besides declarations, the file indicates, in comments, the origin of
1646 each declaration (source file and line), whether the declaration was
1882 might compile a file @code{firstClass.C} like this:
2623 For example, you might compile a file @code{some_class.m} like this:
2755 the resulting object file, and allow @command{dyld(1)} to load it in at
2757 debugging mode, where the object file in question may be recompiled and
2777 Dump interface declarations for all classes seen in the source file to a
2778 file named @file{@var{sourcename}.decl}.
3144 If a source file was changed between @option{-fprofile-gen} and
3146 to match the source file and GCC cannot use the profile feedback
4752 object file, emit it in all object files using the class. This option
4812 way of storing compiler options into the object file.
4819 @item -gstrict-dwarf
4820 @opindex gstrict-dwarf
4825 @item -gno-strict-dwarf
4826 @opindex gno-strict-dwarf
4873 @item -fdump-final-insns@r{[}=@var{file}@r{]}
4875 Dump the final internal representation (RTL) to @var{file}. If the
4876 optional argument is omitted (or if @var{file} is @code{.}), the name
4877 of the dump file will be determined by appending @code{.gkd} to the
4878 compilation output file name.
4930 only when the base name of the compilation source file
4931 matches the base name of file in which the struct was defined.
4942 only when the base name of the compilation source file
4943 matches the base name of file in which the type was defined,
4986 the base of name of the file in which the type declaration appears
4987 must match the base of the name of the main compilation file.
4989 types declared in @file{foo.c} and @file{foo.h} will have debug information,
5006 of the debug information in the output file at the cost of increasing
5011 When compiling files in directory @file{@var{old}}, record debugging
5012 information describing them as in @file{@var{new}} instead.
5062 @file{.su} to the @var{auxname}. @var{auxname} is generated from the name of
5063 the output file, if explicitly specified and it is not an executable,
5064 otherwise it is the basename of the source file. An entry is made up
5096 program exits it saves this data to a file called
5097 @file{@var{auxname}.gcda} for each source file. The data may be used for
5099 test coverage analysis (@option{-ftest-coverage}). Each object file's
5100 @var{auxname} is generated from the name of the output file, if
5102 the basename of the source file. In both cases any suffix is removed
5103 (e.g.@: @file{foo.gcda} for input file @file{dir/foo.c}, or
5104 @file{dir/foo.gcda} for output file specified as @option{-o dir/foo.o}).
5122 every source file in a program.
5131 concurrent instances of your program, and provided that the file system
5144 information from the @file{.gcno} and @file{.gcda} files. Refer to the
5160 Produce a notes file that the @command{gcov} code-coverage utility
5162 show program coverage. Each source file's note file is called
5163 @file{@var{auxname}.gcno}. Refer to the @option{-fprofile-arcs} option
5209 function header of a dump file, and the pass names can be dumped by using
5258 compiler. The file names for most of the dumps are made by appending
5260 created in the directory of the output file. Note that the pass
5265 @var{dumpname} is generated from the name of the output file, if
5267 basename of the source file. These switches may have different effects
5490 Dump after conversion from GCC's "flat register file" registers to the
5562 to @file{@var{file}.@var{pass}.vcg}.
5594 unit to a file. The file name is made by appending @file{.tu} to the
5595 source file name, and the file is created in the same directory as the
5596 output file. If the @samp{-@var{options}} form is used, @var{options}
5604 table layout to a file. The file name is made by appending
5605 @file{.class} to the source file name, and the file is created in the
5606 same directory as the output file. If the @samp{-@var{options}} form
5613 language tree to a file. The file name is generated by appending a
5614 switch specific suffix to the source file name, and the file is created
5615 in the same directory as the output file. The following dumps are
5638 Enable and control dumping of pass statistics in a separate file. The
5639 file name is generated by appending a suffix ending in
5640 @samp{.statistics} to the source file name, and the file is created in
5641 the same directory as the output file. If the @samp{-@var{option}}
5651 language tree to a file. The file name is generated by appending a
5652 switch specific suffix to the source file name, and the file is
5653 created in the same directory as the output file. If the
5662 changes according to the environment and source file. Its primary use
5663 is for tying up a dump file with a debug environment.
5667 use working backward from mangled names in the assembly file.
5705 Dump before any tree based optimization, to @file{@var{file}.original}.
5709 Dump after all tree based optimization, to @file{@var{file}.optimized}.
5713 Dump each function before and after the gimplification pass to a file. The
5714 file name is made by appending @file{.gimple} to the source file name.
5718 Dump the control flow graph of each function to a file. The file name is
5719 made by appending @file{.cfg} to the source file name.
5723 Dump the control flow graph of each function to a file in VCG format. The
5724 file name is made by appending @file{.vcg} to the source file name. Note
5725 that if the file contains more than one function, the generated file cannot
5727 graph into its own separate file first.
5731 Dump each function after copying loop headers. The file name is made by
5732 appending @file{.ch} to the source file name.
5736 Dump SSA related information to a file. The file name is made by appending
5737 @file{.ssa} to the source file name.
5741 Dump aliasing information for each function. The file name is made by
5742 appending @file{.alias} to the source file name.
5746 Dump each function after CCP@. The file name is made by appending
5747 @file{.ccp} to the source file name.
5751 Dump each function after STORE-CCP@. The file name is made by appending
5752 @file{.storeccp} to the source file name.
5756 Dump trees after partial redundancy elimination. The file name is made
5757 by appending @file{.pre} to the source file name.
5761 Dump trees after full redundancy elimination. The file name is made
5762 by appending @file{.fre} to the source file name.
5766 Dump trees after copy propagation. The file name is made
5767 by appending @file{.copyprop} to the source file name.
5771 Dump trees after store copy-propagation. The file name is made
5772 by appending @file{.store_copyprop} to the source file name.
5776 Dump each function after dead code elimination. The file name is made by
5777 appending @file{.dce} to the source file name.
5781 Dump each function after adding mudflap instrumentation. The file name is
5782 made by appending @file{.mudflap} to the source file name.
5787 file name is made by appending @file{.sra} to the source file name.
5791 Dump each function after performing code sinking. The file name is made
5792 by appending @file{.sink} to the source file name.
5796 Dump each function after applying dominator tree optimizations. The file
5797 name is made by appending @file{.dom} to the source file name.
5801 Dump each function after applying dead store elimination. The file
5802 name is made by appending @file{.dse} to the source file name.
5806 Dump each function after optimizing PHI nodes into straightline code. The file
5807 name is made by appending @file{.phiopt} to the source file name.
5811 Dump each function after forward propagating single use variables. The file
5812 name is made by appending @file{.forwprop} to the source file name.
5816 Dump each function after applying the copy rename optimization. The file
5817 name is made by appending @file{.copyrename} to the source file name.
5822 generic trees. The file name is made by appending @file{.nrv} to the source
5823 file name.
5827 Dump each function after applying vectorization of loops. The file name is
5828 made by appending @file{.vect} to the source file name.
5832 Dump each function after applying vectorization of basic blocks. The file name
5833 is made by appending @file{.slp} to the source file name.
5837 Dump each function after Value Range Propagation (VRP). The file name
5838 is made by appending @file{.vrp} to the source file name.
5850 in which case it is output to the usual dump listing file, @file{.vect}.
5877 that have to be different in every compiled file. It is also used to
5882 The @var{string} should be different for every file you compile.
5890 to the usual dump listing file, @file{.sched1} or @file{.sched2}
5906 in the current directory and name them based on the source file. Thus,
5907 compiling @file{foo.c} with @samp{-c -save-temps} would produce files
5908 @file{foo.i} and @file{foo.s}, as well as @file{foo.o}. This creates a
5909 preprocessed @file{foo.i} output file even though the compiler now
5914 input source file with the same extension as an intermediate file.
5915 The corresponding intermediate file may be obtained by renaming the
5916 source file before using @option{-save-temps}.
5920 same source file compiled for multiple output destinations, it is
5929 may result in @file{foo.i} and @file{foo.o} being written to
5936 object file. If the @option{-o} option is not used, the
5947 would create @file{foo.i}, @file{foo.s}, @file{dir/xbar.i},
5948 @file{dir/xbar.s}, @file{dir2/yfoobar.i}, @file{dir2/yfoobar.s}, and
5949 @file{dir2/yfoobar.o}.
5951 @item -time@r{[}=@var{file}@r{]}
5957 Without the specification of an output file, the output looks like this:
5969 With the specification of an output file, the output is appended to the
5970 named file, and it looks like this:
5979 can later tell what file was being compiled, and with which options.
6008 @item -print-file-name=@var{library}
6009 @opindex print-file-name
6010 Print the full absolute name of the library file @var{library} that
6013 file name.
6032 multilib, relative to some @file{lib} subdirectory. If OS libraries are
6033 present in the @file{lib} subdirectory and no multilibs are used, this is
6034 usually just @file{.}, if OS libraries are present in @file{lib@var{suffix}}
6035 sibling directories this prints e.g.@: @file{../lib64}, @file{../lib} or
6036 @file{../lib32}, or if OS libraries are present in @file{lib/@var{subdir}}
6037 subdirectories it prints e.g.@: @file{amd64}, @file{sparcv9} or @file{ev6}.
6042 relative to some @file{lib} subdirectory.
6046 Like @option{-print-file-name}, but searches for a program such as @samp{cpp}.
6048 @item -print-libgcc-file-name
6049 @opindex print-libgcc-file-name
6050 Same as @option{-print-file-name=libgcc.a}.
6053 but you do want to link with @file{libgcc.a}. You can do
6056 gcc -nostdlib @var{files}@dots{} `gcc -print-libgcc-file-name`
6065 @samp{installation problem, cannot exec cpp0: No such file or directory}.
6066 To resolve this you either need to put @file{cpp0} and the other compiler
6111 for types that are nowhere used in the source file being compiled.
6134 program. Compiling multiple files at once to a single output file mode allows
6460 into the object file, even if the function has been inlined into all
6463 inline functions into the object file.
6557 library (@file{libmudflap}), which will be linked into a program if
6824 Control the verbosity of the dump file for the integrated register allocator.
7588 Reorder functions in the object file in order to
7592 the linker so object file format must support named sections and linker must
7768 input file. When this option is used, unreferenced static variables
7793 …objects according to resolution file produced by @command{gold}. For other linkers that cannot ge…
7795 programs consisting of a single file, in combination with option
7798 local for the whole combined compilation unit, not for the single source file
7801 This option implies @option{-fwhole-file} for Fortran programs.
7808 file. When the object files are linked together, all the function
7822 of GIMPLE into special ELF sections inside @file{foo.o} and
7823 @file{bar.o}. The final invocation reads the GIMPLE bytecode from
7824 @file{foo.o} and @file{bar.o}, merges the two files into a single
7826 @file{foo.o} and @file{bar.o} are merged into a single image, this
7830 @file{bar.o} into functions in @file{foo.o} and vice-versa.
7838 The above generates bytecode for @file{foo.c} and @file{bar.c},
7840 them as usual to produce @file{myprog}.
7856 Note that when a file is compiled with @option{-flto}, the generated
7857 object file is larger than a regular object file because it
7873 code, but the resulting binary @file{myprog} is optimized at
7875 @option{-flto}, then @file{myprog} is not optimized.
7893 values (e.g., one file is compiled with @option{-fPIC} and another
7924 @file{libfoo.a}, it is possible to extract and use them in an LTO link if you
7933 GIMPLE files from @file{libfoo.a} and passes them on to the running GCC
7937 enable the linker plugin, then the objects inside @file{libfoo.a}
8071 profile data file will appear in the same directory as the object file.
8347 counts to a file called @file{@var{sourcename}.gcda} for each source
8348 file. The information in this data file is very dependent on the
8355 used in one place: in @file{reorg.c}, instead of guessing which path a
8439 file if the target supports arbitrary sections. The name of the
8441 in the output file.
9288 file before actual compilation.
9349 an executable output file. They are meaningless if the compiler is
9353 @cindex file names
9354 @item @var{object-file-name}
9355 A file name that does not end in a special recognized suffix is
9356 considered to name an object file or library. (Object files are
9357 distinguished from libraries by the linker according to the file
9368 object file names should not be used as arguments. @xref{Overall
9382 after file @file{foo.o} but before @file{bar.o}. If @file{bar.o} refers
9386 which is actually a file named @file{lib@var{library}.a}. The linker
9387 then uses this file as if it had been specified precisely by name.
9393 whose members are object files. The linker handles an archive file by
9395 been referenced but not defined. But if the file that is found is an
9396 ordinary object file, it is linked in the usual fashion. The only
9397 difference between using an @option{-l} option and specifying a file name
9444 @option{-nodefaultlibs} is @file{libgcc.a}, a library of internal subroutines
9449 for more discussion of @file{libgcc.a}.)
9450 In most cases, you need @file{libgcc.a} even when you want to avoid
9499 On systems that provide @file{libgcc} as a shared library, these options
9501 If no shared version of @file{libgcc} was built when the compiler was
9505 shared @file{libgcc} instead of the static version. The most common
9508 as well as the application itself should use the shared @file{libgcc}.
9516 find that they will not always be linked with the shared @file{libgcc}.
9519 it will link the shared version of @file{libgcc} into shared libraries
9521 away the linking with the shared version of @file{libgcc}, linking with
9530 @file{libgcc}.
9535 @file{libstdc++} is available as a shared library, and the
9537 shared version of @file{libstdc++}. That is normally fine. However, it
9538 is sometimes useful to freeze the version of @file{libstdc++} used by
9541 link @file{libstdc++} statically, without necessarily linking other
9608 file, substituting your own version, since these directories are
9609 searched before the system header file directories. However, you should
9634 "@var{file}"}; they are not searched for @samp{#include <@var{file}>},
9648 @file{cpp}, @file{cc1}, @file{as} and @file{ld}. It tries
9655 @file{/usr/lib/gcc/} and @file{/usr/local/lib/gcc/}. If neither of
9656 those results in a file name that is found, the unmodified program
9671 The runtime support file @file{libgcc.a} can also be searched for using
9673 standard prefixes above are tried, and that is all. The file is left
9681 @file{[dir/]stage@var{N}/}, where @var{N} is a number in the range 0 to
9682 9, then it will be replaced by @file{[dir/]include}. This is to help
9685 @item -specs=@var{file}
9687 Process @var{file} after the compiler reads in the standard @file{specs}
9688 file, in order to override the defaults which the @file{gcc} driver
9689 program uses when determining what switches to pass to @file{cc1},
9690 @file{cc1plus}, @file{as}, @file{ld}, etc. More than one
9691 @option{-specs=@var{file}} can be specified on the command line, and they
9698 @file{/usr/include} and libraries in @file{/usr/lib}, it will instead
9699 search @file{@var{dir}/usr/include} and @file{@var{dir}/usr/lib}.
9707 header file aspect of @option{--sysroot} will still work, but the
9715 option are searched only for the case of @samp{#include "@var{file}"};
9716 they are not searched for @samp{#include <@var{file}>}.
9724 directory (where the current input file came from) as the first search
9725 directory for @samp{#include "@var{file}"}. There is no way to
9751 a spec file.
9760 Issues a @var{command} to the spec file processor. The commands that can
9764 @item %include <@var{file}>
9766 Search for @var{file} and insert its text at the current point in the
9767 specs file.
9769 @item %include_noerr <@var{file}>
9772 file cannot be found.
9795 input file with the named suffix, it will processes the spec string in
9796 order to work out how to compile that file. For example:
9803 This says that any input file whose name ends in @samp{.ZZ} should be
9860 Here is a small example of a spec file:
9890 Substitute the name of the input file being processed.
9893 Substitute the basename of the input file being processed.
9898 This is the same as @samp{%b}, but include the file suffix (text after
9903 temporary file name, so that that file will be deleted if GCC exits
9908 Substitute a file name that has suffix @var{suffix} and is chosen
9910 @samp{%d}. To reduce exposure to denial-of-service attacks, the file
9912 chosen file names are known. For example, @samp{%g.s @dots{} %g.o @dots{} %g.s}
9916 was simply substituted with a file name chosen once per compilation,
9921 Like @samp{%g}, but generates a new temporary file name even if
9925 Substitutes the last file name generated with @samp{%u@var{suffix}}, generating a
9926 new one if there is no such last file name. In the absence of any
9929 would involve the generation of two distinct file names, one
9931 simply substituted with a file name chosen for the previous @samp{%u},
9937 of a temporary file, just like @samp{%u}. This temporary file is not
9948 construct: see for example @file{f/lang-specs.h}.
9957 designated output file of this compilation. This puts the argument
9972 because of the need for those to form complete file names. The
9995 Current argument is the name of a library or startup file of some sort.
9996 Search for that file in a standard list of directories and substitute
10001 Current argument is the name of a linker script. Search for that file
10002 in the current list of directories to scan for libraries. If the file
10004 followed by the full path name found. If the file is not found then
10058 this might be a file named @file{crt0.o}.
10102 example, if @env{TOPDIR} is defined as @file{/path/to/top}, then:
10108 expands to @file{/path/to/top/include}.
10112 pathname to a file. If the file exists, @code{if-exists} returns the
10123 an absolute pathname to a file. If the file exists, @code{if-exists-else}
10125 This way, @code{if-exists-else} can be used to select one file or another,
10188 Like %@{@code{S}@} but mark last argument supplied within as a file to be
10220 Substitutes @code{X}, if processing a file with suffix @code{S}.
10223 Substitutes @code{X}, if @emph{not} processing a file with suffix @code{S}.
10226 Substitutes @code{X}, if processing a file for language @code{S}.
10229 Substitutes @code{X}, if not processing a file for language @code{S}.
10393 @item -mhalf-reg-file
10394 @opindex mhalf-reg-file
10482 object file outweighs the size and speed overhead for any extra
10888 Gives all externally visible functions in the file being compiled an ARM
10950 generated object file to either true or false, depending upon the
11792 assembly file.
11921 an object file for the single architecture that it was built to
11925 @file{lipo}.
11927 The subtype of the file created (like @samp{ppc7400} or @samp{ppc970} or
11933 mismatch. The assembler, @file{as}, will only permit instructions to
11934 be used that are valid for the subtype of the file it is generating,
11935 so you cannot put 64-bit instructions in a @samp{ppc750} object file.
11936 The linker for shared libraries, @file{/usr/bin/libtool}, will fail
11939 a @samp{ppc970} object file in a @samp{ppc7400} library). The linker
11940 for executables, @file{ld}, will quietly give the executable the most
12046 Causes the output file to be marked such that the dynamic linker will
12047 bind all undefined references when the file is loaded or launched.
12051 Produce a Mach-o bundle format file.
12057 output file being linked. See man ld(1) for more information.
12062 an executable when linking, using the Darwin @file{libtool} command.
12066 This causes GCC's output file to have the @var{ALL} subtype, instead of
12074 @itemx -dependency-file
12137 @opindex dependency-file
12206 functions in @file{libgcc.a} will be used to perform floating-point
12341 generated assembly file. Under DEC Unix, this has the effect that
12556 to include the simulator library (@file{libsim.a}) on the linker
12972 @file{/usr/lib/sched.models} on an HP-UX system to determine the proper
13051 to @file{/usr/lib/sched.models} on an HP-UX system to determine the
13070 @option{-msoft-float} changes the calling convention in the output file;
13072 this option. In particular, you need to compile @file{libgcc.a}, the
13147 and @code{_XOPEN_SOURCE_EXTENDED}, and the startfile @file{unix95.o}.
13150 @code{_INCLUDE_XOPEN_SOURCE_500}, and the startfile @file{unix98.o}.
13689 the file containing the CPU detection code should be compiled without
14045 specifies that the GNU extension to the PE file format that
14400 example, file I/O@. You must not use this option when generating
14916 object file that accesses more than 8192 GOT entries. Very few do.
14990 simulator library (@file{libsim.a)} from the linker command line.
15239 normal executable (default), uses startup code @file{crt0.o}.
15243 software intrusive debug agent called xmdstub. This uses startup file
15244 @file{crt1.o} and sets the start address of the program to be 0x800.
15248 This model uses startup file @file{crt2.o} which does not contain a processor
15255 within a monitoring application. This model uses @file{crt3.o} as a startup file.
15520 file accesses more than 64k's worth of GOT entries. Very few do.
15912 @file{libgcc.a}. At present, these functions are only provided by
16242 Do not link in the C run-time initialization object file.
16789 every executable file. The @option{-mfull-toc} option is selected by
16807 GCC to make only one TOC entry for every file. When you specify this
16849 standard location (@file{/usr/lpp/ppe.poe/}), or the @file{specs} file
17182 @file{sim-crt0.o} and that the standard C libraries are @file{libsim.a} and
17183 @file{libc.a}. This is the default for @samp{powerpc-*-eabisim}
17189 @file{crt0.o} and the standard C libraries are @file{libmvme.a} and
17190 @file{libc.a}.
17195 @file{crt0.o} and the standard C libraries are @file{libads.a} and
17196 @file{libc.a}.
17201 @file{crt0.o} and the standard C libraries are @file{libyk.a} and
17202 @file{libc.a}.
17639 functions in @file{libgcc.a} will be used to perform floating-point
17649 specified, functions in @file{libgcc.a} will be used to perform
18352 @option{-msoft-float} changes the calling convention in the output file;
18354 this option. In particular, you need to compile @file{libgcc.a}, the
18787 Refrain from adding @code{.ident} directives to the output file (this is
19098 section in the output file. This allows the literal pool to be placed
19137 every cross-file call, not just those that really will be out of range.
19294 uninitialized global variables in the data section of the object file,
19314 used when compiling @file{crtstuff.c}; you should not need to use it
19331 compiler to be recorded into the object file that is being created.
19333 of the recording is target and binary file format dependent, but it
19336 switch only records information in the assembler output file as
19337 comments, so it never reaches the object file.
19339 way of storing compiler options into the object file.
19407 macro in the machine description macro file.
19494 @item -finstrument-functions-exclude-file-list=@var{file},@var{file},@dots{}
19495 @opindex finstrument-functions-exclude-file-list
19498 the description of @code{-finstrument-functions}). If the file that
19499 contains a function definition matches with one of @var{file}, then
19501 if the @var{file} parameter is a substring of the file name, it is
19507 -finstrument-functions-exclude-file-list=/bits/stl,include/sys
19516 @code{-finstrument-functions-exclude-file-list='\,\,tmp'}
19522 This is similar to @code{-finstrument-functions-exclude-file-list},
19610 change the way C symbols are represented in the object file. One use
19742 @xref{Driver,, Controlling the Compilation Driver @file{gcc}, gccint,
19814 @file{@var{prefix}/lib/gcc/} where @var{prefix} is the prefix to
19816 of @code{prefix} when you ran the @file{configure} script.
19820 This prefix is also used for finding files such as @file{crt0.o} that are
19829 @file{foo/bar} where it would normally search @file{/usr/local/lib/bar}.
19889 source file. The time the compiler takes to process these header files
19892 `precompile' a header file; then, if builds can use the precompiled
19893 header file they will be much faster.
19895 To create a precompiled header file, simply compile it as you would any
19896 other file, if necessary using the @option{-x} option to make the driver
19897 treat it as a C or C++ header file. You will probably want to use a
19901 A precompiled header file will be searched for when @code{#include} is
19902 seen in the compilation. As it searches for the included file
19905 looks for the include file in that directory. The name searched for is
19907 the precompiled header file can't be used, it is ignored.
19910 @file{all.h.gch} in the same directory as @file{all.h}, then the
19911 precompiled header file will be used if possible, and the original
19914 Alternatively, you might decide to put the precompiled header file in a
19917 Then, if you want to check that the precompiled header file is always
19918 used, you can put a file of the same name as the original header in this
19924 a project, include them from another header file, precompile that header
19925 file, and @option{-include} the precompiled header. If the header files
19929 If you need to precompile the same header file for different
19931 @emph{directory} named like @file{all.h.gch}, and put each precompiled
19941 A precompiled header file can be used only when these conditions apply:
19954 The precompiled header file must be produced for the same language as
19959 The precompiled header file must have been produced by the same compiler