On Sun, Oct 14, 2001 at 01:38:45AM +0100, Sean Neakums wrote:
> begin Nigel Kukard quotation:
>
> > On Sun, 14 Oct 2001, Seth Mos wrote:
> >> error 990 means that it detected corruption. Something is horribly
> >> wrong in this case if it happens a lot. What compiler did you
> >> use. (Use egcs-1.1.2 == 2.91.66 for production systems)
> >
> > [nkukard@devel source]$ gcc -v
> > Reading specs from /usr/lib/gcc-lib/i586-pc-linux/2.96/specs
> > gcc version 2.96 20000731 (IDMS Linux 2.96-5)
> >
> > that is basically the same "strain" of gcc that redhat use as i
> > pulled it out their srpm a few months ago.
>
> Try using an offical official GCC release. I've been using GCC 2.95
> for a month or so with no problems. Before that I used the release of
> GCC suggested above by Seth. GCC 2.96 as shipped by Red Hat is an
> unofficial release of the GCC-3.0 CVS development branch.
>
> The ONLY grief I have had with XFS from CVS is on an untried platform
> with an untried compiler. GCC 2.95 on IA-32 should be trouble-free.
Except that it's not. With gcc 2.95 and -mcpu=pentiumpro -march=pentiumpro,
I have seen instructions from asm statements reordered around those generated
from C by the compiler. The consequences of this in kernel code can be quite
dire!
Also, didn't the SGI folks just strongly advise, once again, the use of
2.91 and 2.91 *only*?
Thor
|