From: pavenis AT lanet DOT lv
To: "Mark E." <snowball3 AT bigfoot DOT com>, djgpp-workers AT delorie DOT com
Date: Mon, 26 Jun 2000 15:57:56 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: ANNOUNCE: Binutils 2.10 released
Message-ID: <39577D84.22597.95F1E8@localhost>
In-reply-to: <39572660.13631.1C299E@localhost>
References: <Pine DOT A41 DOT 4 DOT 05 DOT 10006261000050 DOT 60198-100000 AT ieva06 DOT lanet DOT lv>
X-mailer: Pegasus Mail for Win32 (v3.12c)
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
Precedence: bulk

On 26 Jun 2000, at 9:46, Mark E. wrote:

> > We can make it also as the default in gcc. So if one wants to use old
> > binutils due to some reason, he/she may specify -fno-bnu210.
> > 
> 
> We can and probably should now that 2.10 is out. But there may also be subtle 
> problems for C++ users who still use < 2.10 by doing this. But then again any 
> serious C++ user already has a problem with using C++ templates if they don't 
> upgrade to 2.10.
> 
> On a rather disturbing note, I discovered late last night some C++ programs 
> crash when built under 2.10, but C programs run fine. I think I know what 
> needs to be fixed, but when I do fix it I'll have to re-upload Binutils 2.10 
> (sorry).
> 

I haven't noticed such behaviour with C++ and binutils-2.10 (I'm not 
using "official" bnu210b.zip though but my own binaries I built using
cross-compiling under Linux).

Andris

PS. I'm leaving in wednesday for some time, but I think  I'll be reading 
e-mail and I'll be able to do some tests.