gcc.texinfo

这是完整的gcc源代码

Dump after first jump optimization.
@item s
Dump after CSE (including the jump optimization that sometimes
follows CSE).
@item L
Dump after loop optimization.
@item f
Dump after flow analysis.
@item c
Dump after instruction combination.
@item l
Dump after local register allocation.
@item g
Dump after global register allocation.
@item d
Dump after delayed branch scheduling.
@item J
Dump after last jump optimization.
@item m
Print statistics on memory usage, at the end of the run.
@end table

@item -pedantic
Issue all the warnings demanded by strict ANSI standard C; reject
all programs that use forbidden extensions.

Valid ANSI standard C programs should compile properly with or without
this option (though a rare few will require @samp{-ansi}).  However,
without this option, certain GNU extensions and traditional C features
are supported as well.  With this option, they are rejected.  There is
no reason to @i{use} this option; it exists only to satisfy pedants.

@samp{-pedantic} does not cause warning messages for use of the
alternate keywords whose names begin and end with @samp{__}.
@xref{Alternate Keywords}.

@item -static
On Suns running version 4, this prevents linking with the shared
libraries.  (@samp{-g} has the same effect.)
@end table

These options control the C preprocessor, which is run on each C source
file before actual compilation.  If you use the @samp{-E} option, nothing
is done except C preprocessing.  Some of these options make sense only
together with @samp{-E} because they request preprocessor output that is
not suitable for actual compilation.

@table @samp
@item -C
Tell the preprocessor not to discard comments.  Used with the
@samp{-E} option.

@item -I@var{dir}
Search directory @var{dir} for include files.

@item -I-
Any directories specified with @samp{-I} options before the @samp{-I-}
option are searched only for the case of @samp{#include "@var{file}"};
they are not searched for @samp{#include <@var{file}>}.

If additional directories are specified with @samp{-I} options after
the @samp{-I-}, these directories are searched for all @samp{#include}
directives.  (Ordinarily @emph{all} @samp{-I} directories are used
this way.)

In addition, the @samp{-I-} option inhibits the use of the current
directory (where the current input file came from) as the first search
directory for @samp{#include "@var{file}"}.  There is no way to override
this effect of @samp{-I-}.  With @samp{-I.} you can specify searching
the directory which was current when the compiler was invoked.  That is
not exactly the same as what the preprocessor does by default, but it is
often satisfactory.

@samp{-I-} does not inhibit the use of the standard system directories
for header files.  Thus, @samp{-I-} and @samp{-nostdinc} are
independent.

@item -i @var{file}
Process @var{file} as input, discarding the resulting output, before
processing the regular input file.  Because the output generated from
@var{file} is discarded, the only effect of @samp{-i @var{file}} is to
make the macros defined in @var{file} available for use in the main
input.

@item -nostdinc
Do not search the standard system directories for header files.  Only
the directories you have specified with @samp{-I} options (and the
current directory, if appropriate) are searched.

Between @samp{-nostdinc} and @samp{-I-}, you can eliminate all
directories from the search path except those you specify.

@item -M
Tell the preprocessor to output a rule suitable for @code{make}
describing the dependencies of each object file.  For each source
file, the preprocessor outputs one @code{make}-rule whose target is
the object file name for that source file and whose dependencies are
all the files @samp{#include}d in it.  This rule may be a single line
or may be continued with @samp{\}-newline if it is long.

@samp{-M} implies @samp{-E}.

@item -MM
Like @samp{-M} but the output mentions only the user-header files
included with @samp{#include "@var{file}"}.  System header files
included with @samp{#include <@var{file}>} are omitted.

@samp{-MM} implies @samp{-E}.

@item -D@var{macro}
Define macro @var{macro} with the  string @samp{1} as its definition.

@item -D@var{macro}=@var{defn}
Define macro @var{macro} as @var{defn}.

@item -U@var{macro}
Undefine macro @var{macro}.

@item -trigraphs
Support ANSI C trigraphs.  You don't want to know about this
brain-damage.  The @samp{-ansi} option also has this effect.
@end table

@node Installation, Trouble, Options, Top
@chapter Installing GNU CC

Here is the procedure for installing GNU CC on a Unix system.

@menu
* Other Dir::     Compiling in a separate directory (not where the source is).
* Sun Install::   See below for installation on the Sun.
* 3B1 Install::   See below for installation on the 3B1.
* SCO Install::   See below for installation on SCO System V 3.2.  (Or ESIX.)
* VMS Install::   See below for installation on VMS.
* HPUX Install::  See below for installation on HPUX.
* Tower Install:: See below for installation on an NCR Tower.
@end menu
@iftex
See below for VMS systems, and modified procedures needed on Sun
systems, 3b1 machines and HPUX.  The following section says how to
compile in a separate directory on Unix; here we assume you compile in
the same directory that contains the source files.
@end iftex

@enumerate
@item
Edit @file{Makefile}.  If you are using HPUX, or any form of system V,
you must make a few changes described in comments at the beginning of
the file.  Genix requires changes also, and so does the Pyramid.

@item
On a Sequent system, go to the Berkeley universe.

@item
Choose configuration files.  The easy way to do this is to run the
command file @file{config.gcc} with a single argument, which specifies
the type of machine (and in some cases which operating system).

Here is a list of the possible arguments:

@table @samp
@item vax
Vaxes running BSD.
@item vms
Vaxes running VMS.
@item vax-sysv
Vaxes running system V.
@item i386-sysv
Intel 386 PCs running system V.
@item i386-sysv-gas
Intel 386 PCs running system V, using the GNU assembler and GNU
linker.
@item i386-sysv4
Intel 386 PCs running system V.4.  You must run the shell script
@file{fixincludes-V4} in order for GNU CC to work properly.  You must
also uncomment some lines in @file{Makefile}.
@item sequent-i386
Sequent with Intel 386 processors.
@item i386-aix
Intel 386 PCs or PS/2s running AIX.
@item sun2
Sun 2 running system version 2 or 3.
@item sun3
Sun 3 running system version 4, with 68881.
Note there we do not provide a configuration file to use an FPA
by default, because programs that establish signal handlers for
floating point traps inherently cannot work with the FPA.
@item sun3-nfp
Sun 3 running system version 4, without 68881.
@item sun4
Sun 4 running system version 4.  @xref{Incompatibilities},
for calling convention incompatibilities on the Sun 4 (sparc).
@item sun2-os4
Sun 2 running system version 4.
@item sun3-os3
Sun 3 running system version 2 or 3, with 68881.
@item sun3-nfp-os3
Sun 3 running system version 2 or 3, without 68881.
@item sun4-os3
Sun 4 running system version 2 or 3.  @xref{Incompatibilities},
for calling convention incompatibilities on the Sun 4 (sparc).
@item sun386
Sun 386 (``roadrunner'').
@item alliant
Alliant FX/8 computer.  Note that the standard installed C compiler in
Concentrix 5.0 has a bug which prevent it from compiling GNU CC
correctly.  You can patch the compiler bug as follows:

@example
cp /bin/pcc ./pcc
adb -w ./pcc - << EOF
15f6?w 6610
EOF
@end example

Then you must use the @samp{-ip12} option when compiling GNU CC
with the patched compiler, as shown here:

@example
make CC="./pcc -ip12" CFLAGS=-w
@end example

Note also that Alliant's version of DBX does not manage to work with the
output from GNU CC.
@item tahoe
The tahoe computer (running BSD, and using DBX).
@item decstation
The DEC 3100 Mips machine (``pmax'').  Note that GNU CC cannot generate
debugging information in the unusual format used on the Mips.
@item mips-sysv-os5
The Mips computer, RS series, with the System V environment
running on revision 5.00 of RISC-OS as default.
Note that GNU CC cannot generate debugging information in the unusual
format used on the Mips, and also cannot be used to create
programs that use shared libraries.
@item mips-sysv
The Mips computer, RS series, with the System V environment as default.
Note that GNU CC cannot generate debugging information in the unusual
format used on the Mips.
@item mips-bsd43-os5
The Mips computer, RS series, with the BSD 4.3 environment
running revision 5.00 of RISC-OS as default.
Note that GNU CC cannot generate debugging information in the unusual
format used on the Mips, and also cannot be used to create
programs that use shared libraries.
@item mips-bsd43
The Mips computer, RS series, with the BSD 4.3 environment as default.
Note that GNU CC cannot generate debugging information in the unusual
format used on the Mips.
@item mips-os5
The Mips computer, M series running revision 5.00 of RISC-OS.
Note that GNU CC cannot generate debugging information in the
unusual format used on the Mips, and also cannot be used to
create programs that use shared libraries.
@item mips
The Mips computer, M series.  Note that GNU CC cannot generate debugging
information in the unusual format used on the Mips.
@item iris
Another variant of the Mips computer, the Silicon Graphics Iris 4D.
Note that GNU CC cannot generate debugging information in the unusual
format used on the Mips.
@item convex-c1
Convex C1 computer.  With operating system version 9, use @samp{cc -pcc}
as the compilation command when building stage 1 of GNU CC.
@item convex-c2
Convex C2 computer.  With operating system version 9, use @samp{cc -pcc}
as the compilation command when building stage 1 of GNU CC.
@item pyramid
Pyramid computer.
@item hp9k320
HP 9000 series 300 using HPUX assembler.  Note there is no
support in GNU CC for HP's debugger; thus, @samp{-g} is not
available in this configuration.
@item hp9k320-gas
HP 9000 series 300 using GNU assembler, linker and debugger.
This requires the HP-adapt package, which is available along with
the GNU linker as part of the ``binutils'' distribution.
This is on the GNU CC distribution tape.
@item hp9k320-old
HP 9000 series 300 using HPUX assembler, in operating system versions
older than 6.5.  Note there is no support in GNU CC for HP's debugger;
thus, @samp{-g} is not available in this configuration.
@item hp9k320-bsd
HP 9000 series 300 running BSD.
@item hp9k200-bsd
HP 9000 series 200 running BSD.  Note that the C compiler that comes
with this system cannot compile GNU CC; contact @code{law@@super.org} to
get binaries of GNU CC for bootstrapping.  Additionally, a minor patch
is necessary if you wish to build kernels with GNU CC; contact
@code{law@@super.org} to get a copy of the patch.
@item isi68
ISI 68000 or 68020 system with a 68881.
@item isi68-nfp
ISI 68000 or 68020 system without a 68881.
@item news800
Sony NEWS 68020 system.
@item next
NeXT system.
@item tower
NCR Tower 32 system.
@item altos
Altos 3068.  Note that you must use the GNU assembler, linker and
debugger, with COFF-encapsulation.  Also, you must fix a kernel
bug.  Details in the file @file{ALTOS-README}.
@item 3b1
AT&T 3b1, a.k.a. 7300 PC.  Note that special procedures are needed
to compile GNU CC with this machine's standard C compiler, due to
bugs in that compiler.  @xref{3b1 Install}.  You can bootstrap it
more easily with previous versions of GNU CC if you have them.
@item 3b1-gas
AT&T 3b1 using the GNU assembler.
@item sequent-ns32k
Sequent containing ns32000 processors.
@item encore
Encore ns32000 system.
@item genix
National Semiconductor ns32000 system.
@item 88000
Motorola 88000 processor.  This port is not finished.
@end table

Here we spell out what files need to be set up:

@itemize @bullet
@item
Make a symbolic link named @file{config.h} to the top-level
config file for the machine you are using (@pxref{Config}).  This
file is responsible for defining information about the host
machine.  It includes @file{tm.h}.

The file is located in the subdirectory @file{config}.  Its name
should be @file{xm-@var{machine}.h}, with these exceptions:

@table @file
@item xm-vms.h
for vaxen running VMS.
@item xm-vaxv.h
for vaxen running system V.
@item xm-i386v.h
for Intel 80386's running system V.
@item xm-sun386i.h
for Sun roadrunner running any version of the operating system.
@item xm-hp9k320.h
for the