This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs-release branch aborts during bootstrap
- To: Manfred dot Hollstein at ks dot sel dot alcatel dot de
- Subject: Re: egcs-release branch aborts during bootstrap
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 03 Mar 1998 02:07:14 -0700
- cc: robertl at dgii dot com, egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <9802130736.AA06633@lts.sel.alcatel.de>you write:
> On Thu, 12 February 1998, 15:28:22, robertl@dgii.com wrote:
>
> > [ Manfred, does this fail on your COFF target? ]
> >
> > This command works on the trunk. It fails on the release tag.
> > The sources of the release branch were checked out last night, and
> > a 'cvs update -n' in gcc/cp doesn't show any updates pending. It
> > shows up in a make boostrap2 on OpenServer.
> >
> > (robertl) rjlhome:/play/egcs-release/native/gcc
> > $ cat /tmp/cc
> > ./xgcc -B./ -O2 -DIN_GCC -O2 -g -I./include -g1 \
> > -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -fexceptions \
> > -I. -I../../egcs/gcc -I../../egcs/gcc/config -mcoff \
> > -c ../../egcs/gcc/cp/tinfo.cc
> > (robertl) rjlhome:/play/egcs-release/native/gcc
> > $ sh /tmp/cc
> > include/exception: In method `bad_exception::bad_exception()':
> > In file included from include/typeinfo:7,
> > from ../../egcs/gcc/cp/tinfo.h:4,
> > from ../../egcs/gcc/cp/tinfo.cc:29:
> > include/exception:24: Internal compiler error.
> > include/exception:24: Please submit a full bug report to `egcs-bugs@cygn
> us.com'.
> >
> > If I change '-fexceptions' to '-fno-exceptions' it doesn't crash.
> >
> > If I remove -mcoff, (defaulting back to ELF) it doesn't crash. The core
> > dumps aren't readable by GDB. Whether this is a GDB problem or an EGCS
> > problem is a different mystery.
>
> With my patch `[980205]: Patch for wrong mangling (was: Re: [980129]:
> bug in COFF's name mangling?)' submitted on Mon, 9 Feb 98 12:25:39
> +0100 applied I don't get any such failures; but this is still the
> 980205 snapshot, I still don't have access to CVS :-(
>
> BTW, did you try the patch?
Where do we stand on this problem? Is it still aborting in the release
branch?
jeff