diff options
| author | Richard Guenther <rguenther@suse.de> | 2009-01-02 10:39:59 +0000 |
|---|---|---|
| committer | Laurent Guerby <guerby@gcc.gnu.org> | 2009-01-02 10:39:59 +0000 |
| commit | 00f39bd53c97895bfd525824b421d9656df398d8 (patch) | |
| tree | 04cc0ec02273247bfcce773773a1fa9bc57f6cf9 /gcc/doc | |
| parent | e57fcb68218703aeb8e6194ee0560736d51c61e6 (diff) | |
| download | gcc-00f39bd53c97895bfd525824b421d9656df398d8.zip gcc-00f39bd53c97895bfd525824b421d9656df398d8.tar.gz gcc-00f39bd53c97895bfd525824b421d9656df398d8.tar.bz2 | |
install.texi (--enable-checking): Mention different default for stage1.
2009-01-02 Richard Guenther <rguenther@suse.de>
* doc/install.texi (--enable-checking): Mention different
default for stage1.
(--enable-stage1-checking): Document.
From-SVN: r143007
Diffstat (limited to 'gcc/doc')
| -rw-r--r-- | gcc/doc/install.texi | 16 |
1 files changed, 15 insertions, 1 deletions
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index a218065..5bf25a1 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -1323,7 +1323,8 @@ consistency checks of the requested complexity. This does not change the generated code, but adds error checking within the compiler. This will slow down the compiler and may only work properly if you are building the compiler with GCC@. This is @samp{yes} by default when building -from SVN or snapshots, but @samp{release} for releases. More control +from SVN or snapshots, but @samp{release} for releases. The default +for building the stage1 compiler is @samp{yes}. More control over the checks may be had by specifying @var{list}. The categories of checks available are @samp{yes} (most common checks @samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at @@ -1342,6 +1343,19 @@ assertions will make the compiler and runtime slightly faster but increase the risk of undetected internal errors causing wrong code to be generated. +@item --disable-stage1-checking +@item --enable-stage1-checking +@itemx --enable-stage1-checking=@var{list} +If no @option{--enable-checking} option is specified the stage1 +compiler will be built with @samp{yes} checking enabled, otherwise +the stage1 checking flags are the same as specified by +@option{--enable-checking}. To build the stage1 compiler with +different checking options use @option{--enable-stage1-checking}. +The list of checking options is the same as for @option{--enable-checking}. +If your system is too slow or too small to bootstrap a released compiler +with checking for stage1 enabled, you can use @samp{--disable-stage1-checking} +to disable checking for the stage1 compiler. + @item --enable-coverage @itemx --enable-coverage=@var{level} With this option, the compiler is built to collect self coverage |