-@c Copyright (C) 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
+@c Copyright (C) 2001, 2002, 2003, 2004, 2006, 2008, 2010
+@c Free Software Foundation, Inc.
@c This is part of the GCC manual.
@c For copying conditions, see the file gcc.texi.
@item dvi
Produce DVI-formatted documentation.
+@item pdf
+Produce PDF-formatted documentation.
+
@item html
Produce HTML-formatted documentation.
@item maintainer-clean
Distclean plus any file that can be generated from other files. Note
that additional tools may be required beyond what is normally needed to
-build gcc.
+build GCC.
@item srcextra
-Generates files in the source directory that do not exist in CVS but
-should go into a release tarball. One example is @file{gcc/java/parse.c}
-which is generated from the CVS source file @file{gcc/java/parse.y}.
+Generates files in the source directory that are not version-controlled but
+should go into a release tarball.
@item srcinfo
@itemx srcman
directory usually for the purpose of generating a release tarball.
@item install
-Installs gcc.
+Installs GCC.
@item uninstall
-Deletes installed files.
+Deletes installed files, though this is not supported.
@item check
Run the testsuite. This creates a @file{testsuite} subdirectory that
has various @file{.sum} and @file{.log} files containing the results of
the testing. You can run subsets with, for example, @samp{make check-gcc}.
-You can specify specific tests by setting RUNTESTFLAGS to be the name
+You can specify specific tests by setting @env{RUNTESTFLAGS} to be the name
of the @file{.exp} file, optionally followed by (for some tests) an equals
and a file wildcard, like:
@end smallexample
Note that running the testsuite may require additional tools be
-installed, such as TCL or dejagnu.
+installed, such as Tcl or DejaGnu.
@end table
The toplevel tree from which you start GCC compilation is not
example, continue a bootstrap after fixing a bug which causes the
stage2 build to crash. It does not provide as good coverage of the
compiler as bootstrapping from scratch, but it ensures that the new
-code is syntactically correct (e.g. that you did not use GCC extensions
+code is syntactically correct (e.g., that you did not use GCC extensions
by mistake), and avoids spurious bootstrap comparison
failures@footnote{Except if the compiler was buggy and miscompiled
- some of the files that were not modified. In this case, it's best
- to use @command{make restrap}.}.
+some of the files that were not modified. In this case, it's best
+to use @command{make restrap}.}.
Other targets available from the top level include:
is running properly. Note that the disk space required by a ``lean''
bootstrap is approximately independent of the number of stages.
-@item stage@var{N}-bubble (@var{N} = 1@dots{}4)
+@item stage@var{N}-bubble (@var{N} = 1@dots{}4, profile, feedback)
Rebuild all the stages up to @var{N}, with the appropriate flags,
``bubbling'' the changes as described above.
-@item all-stage@var{N} (@var{N} = 1@dots{}4)
+@item all-stage@var{N} (@var{N} = 1@dots{}4, profile, feedback)
Assuming that stage @var{N} has already been built, rebuild it with the
appropriate flags. This is rarely needed.
regardless of how it itself was compiled.
@item profiledbootstrap
-Builds a compiler with profiling feedback information. For more
-information, see
+Builds a compiler with profiling feedback information. In this case,
+the second and third stages are named @samp{profile} and @samp{feedback},
+respectively. For more information, see
@ref{Building,,Building with profile feedback,gccinstall,Installing GCC}.
@item restrap
Restart a bootstrap, so that everything that was not built with
the system compiler is rebuilt.
-@item stage@var{N}-start (@var{N} = 1@dots{}4)
+@item stage@var{N}-start (@var{N} = 1@dots{}4, profile, feedback)
For each package that is bootstrapped, rename directories so that,
for example, @file{gcc} points to the stage@var{N} GCC, compiled
with the stage@var{N-1} GCC@footnote{Customarily, the system compiler
- is also termed the @file{stage0} GCC.}.
+is also termed the @file{stage0} GCC.}.
You will invoke this target if you need to test or debug the
-stage@var{N} GCC. If you only need to execute GCC (but you need
+stage@var{N} GCC@. If you only need to execute GCC (but you need
not run @samp{make} either to rebuild it or to run test suites),
you should be able to work directly in the @file{stage@var{N}-gcc}
directory. This makes it easier to debug multiple stages in
OSDN Git Service
