From: Roland McGrath <[EMAIL PROTECTED]>
Date: Sun, 11 Mar 2001 19:10:29 -0500 (EST)
Congratulations, you have found a GCC bug. Run the compilation by hand
with -v -save-temps, and then take the -v output and the .i file and
include them in your bug report to the GCC folks.
Sin
> Do you see any value in testing the version 3 branch for these types of
> problems, or should we test the 2.95 branch?
I guess I only answered half your question. We should definitely make sure
the bugs triggered by the Hurd sources under -O3 get reported and fixed
before a GCC release is mad
> On Sun, Mar 11, 2001 at 07:10:29PM -0500, Roland McGrath wrote:
>
> > If you want to pursue this, you should probably get a recent development
> > snapshot of GCC and see if that crashes using -O3.
>
> Do you see any value in testing the version 3 branch for these types of
> problems, or shou
On Sun, Mar 11, 2001 at 07:10:29PM -0500, Roland McGrath wrote:
> If you want to pursue this, you should probably get a recent development
> snapshot of GCC and see if that crashes using -O3.
Do you see any value in testing the version 3 branch for these types of
problems, or should we test the
Congratulations, you have found a GCC bug. Run the compilation by hand
with -v -save-temps, and then take the -v output and the .i file and
include them in your bug report to the GCC folks.
Note that I tried Red Hat 7's version of gcc-2.96 and it also crashed on
some of the Hurd sources (thoug
