Re: GCC 4.2.0 RC3 Available

["Richard Guenther" <richard dot guenther at gmail dot com>]

On 5/5/07, Richard Guenther <richard.guenther@gmail.com> wrote:
> On 5/5/07, Richard Guenther <richard.guenther@gmail.com> wrote:
> > On 5/5/07, Mark Mitchell <mark@codesourcery.com> wrote:
> > > Richard Guenther wrote:
> > >
> > > >> > Another problem is that --enable-checking hasn't been set to 'release',
> > > >> > so the stage1 binary is too big to run on my ARM systems (and the
> > > >> > compiler will be unnecessarily slower than it needs to be).
> > >
> > > >> Are you sure that we're not building with release-checking only?
> > > >
> > > > stage1 is always built with checking enabled.
> > >
> > > OK.  There's a good chance that both Richard E. and I didn't realize
> > > that (it didn't use to be true).  So, from what you're saying, there
> > > doesn't seem to be an evidence that this is a real problem.
> > >
> > > Do we build stage1 with checking enabled even if --disable-checking is
> > > in effect?  Otherwise, how to do folks like Richard E. that are running
> > > natively on small systems work around this issue?
> >
> > Specifying --disable-stage1-checking should work.  (it's in the toplevel
> > configure)
>
> I see this is not documented, though :/  Richard, can you check if it actually
> works?

And if it does, the following patch documents it.  Ok for the branch?

Richard.

2007-05-05  Richard Guenther  <rguenther@suse.de>

       * doc/install.texi (--disable-stage1-checking): Document.

Attachment: disables1c
Description: Binary data