procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

install.texi (--enable-checking): Mention different default for stage1.

Browse source 
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
This commit is contained in:
Richard Guenther 2009-01-02 10:39:59 +00:00 • committed by Laurent Guerby
parent e57fcb6821
commit 00f39bd53c
2 changed files with 21 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
gcc/ChangeLog
View file

@ -1,3 +1,9 @@
2009-01-02 Richard Guenther <rguenther@suse.de>
* doc/install.texi (--enable-checking): Mention different
default for stage1.
(--enable-stage1-checking): Document.
2009-01-01 Andrew Pinski <pinskia@gmail.com>
PR middle-end/30142

16
gcc/doc/install.texi
View file

@ -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