GCC Internal Compiler Error When Compiling with -pipe
Wed Mar 31 19:45:00 GMT 1999
/usr/H-i586-cygwin32/bin> uname -a
CYGWIN_NT-4.0 TGOODMAN8 20.1 (0.3/1/1) 1998-12-3 20:39:18 i686 unknown
/usr/H-i586-cygwin32/bin> gcc -v
Reading specs from
gcc version egcs-2.91.57 19980901 (egcs-1.1 release)
Is it the wrong compiler version?
I guess I'll try the egcs-1.2 release soon and see if that changes the
> -----Original Message-----
> From: email@example.com
> [ mailto:firstname.lastname@example.org]On Behalf Of Chris Faylor
> Sent: Tuesday, March 02, 1999 10:13 PM
> To: Mumit Khan
> Cc: email@example.com
> Subject: Re: GCC Internal Compiler Error When Compiling with -pipe
> On Sun, Feb 28, 1999 at 10:37:18PM -0600, Mumit Khan wrote:
> >N8TM@aol.com writes:
> >> In a message dated 2/28/99 8:18:03 AM Pacific Standard Time,
> >> firstname.lastname@example.org writes:
> >> << gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -Wall -pipe
> -c capability.c
> >> /home/noer/src/b20/comp-tools/devo/gcc/pexecute.c:245:
> Internal compiler
> >> error in function pexecute >>
> >> I haven't seen this problem since b20.1, although I've had
> configure failures
> >> associated with setting CFLAGS '... -pipe'
> >I couldn't reproduce Todd's problem, so hopefully that
> particular one is
> >fixed. We still have a few more cases that I'm tracking down ...
> >The quality of upcoming egcs-1.1.2 is heaps better as compared to b20
> >in terms of stability and "un-crashability".
> The -pipe problem should have been fixed in B20.1. I
> submitted a patch for
> it myself.
> Want to unsubscribe from this list?
> Send a message to email@example.com
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org
More information about the Cygwin