Date:	Fri, 13 Jul 2001 09:16:45 +0300 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	djgpp-workers AT delorie DOT com
Subject:	Re: Comments on GCC 3.0 distribution
In-Reply-To:	<2110-Thu12Jul2001215820+0300-eliz@is.elta.co.il>
Message-ID:	<Pine.A41.4.05.10107130913220.67752-100000@ieva06.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 12 Jul 2001, Eli Zaretskii wrote:

> > From: pavenis AT lanet DOT lv
> > Date: Thu, 12 Jul 2001 18:48:35 +0300
> > 
> > Builtin script from bnu2112b.zip seems to be compatible with gcc-3.0
> > (all seems to work if I remove -Tdjgpp-x.djl from specs). Anyway
> > problem like:
> > 	All my C++ programs crashes and GDB shows nonsense
> > 	when I'm trying to debug this problem. All worked Ok with
> > 	gcc-2.95.X
> > is too serious to be simply ignored.
> 
> Sorry, I don't understand: is the built-in script _compatible_ with
> GCC 3.0, or is it _incompatible_?  If it is compatible, how come the
> programs crash?
> 

Builtin script from binutils-2.11.2 IS compatible with gcc-3.0. But I'm
completely sure there will be careless users who will try to use it with
binutils-2.11 or before (with incompatible linker scripts). In this case I
would prefer linker or assembler error messages rather than such hard to
debug crashes. This is reason why I still would like to keep linker script
in gcc-3.0 binary archives for some time.

Andris

- Raw text -