Missing commit for --enable-stage1-checking doc patch? (was: GCC compile farm / ARM architecture)

Laurent GUERBY laurent@guerby.net
Fri Jan 2 10:42:00 GMT 2009


On Mon, 2008-12-29 at 17:02 +0100, Richard Guenther wrote:
> On Mon, Dec 15, 2008 at 1:01 PM, Laurent GUERBY <laurent@guerby.net> wrote:
> > Interestingly I went back to check the documentation
> > and Richard Guenther doc patch mentionned here:
> >
> > http://gcc.gnu.org/ml/gcc/2007-05/msg00148.html
> > <<
> > 2007-05-05 Richard Guenther <rguenther@suse.de>
> >
> > * doc/install.texi (--enable-checking): Mention different
> >       default for stage1.
> >       (--enable-stage1-checking): Document.
> >>>
> >
> > Is not present on trunk nor on 4.2 nor on gcc/ChangeLog*
> > and so --enable-stage1-checking is still undocumented
> > (unless I missed something in my greps) while
> > still present in top level configure (and I hope
> > still working but not tested yet).
> >
> > Richard G, do you remember what happened to your doc patch?
> 
> I have no idea.  It probably got "lost".

I've commited the following on trunk as revision 143007
after make info and dvi visual inspection (patch approved a while
ago :).

Laurent

2009-01-02 Richard Guenther <rguenther@suse.de>

       * doc/install.texi (--enable-checking): Mention different
       default for stage1.
       (--enable-stage1-checking): Document.

Index: gcc/doc/install.texi
===================================================================
--- gcc/doc/install.texi	(revision 143006)
+++ gcc/doc/install.texi	(working copy)
@@ -1323,7 +1323,8 @@
 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 @@
 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






More information about the Gcc-patches mailing list