Subject: Re: NOTE: gcc 2.95 import soon
To: Richard Earnshaw <rearnsha@arm.com>
From: Todd Vierling <tv@pobox.com>
List: tech-toolchain
Date: 07/05/2000 10:29:22
On Wed, 5 Jul 2000, Richard Earnshaw wrote:

: Pulling in 2.96 would be, IMO, high risk and we would likely end up with a 
: lot of local modifications to work around bugs which are bound to get 
: fixed in fairly short order in the main tree.

I figured as much on this point, which is why I polled you.  (Given that I
have been allocated primarily to my job for some time, you're a lot more in
tune with the current state of codegen and ICE bugs in gcc at the moment.)

: PS I'd also like to see us reduce the number of in-tree mods that aren't 
: propagated back into the master tree (for example, gcc-2.96 doesn't have a 
: i386-netbsdelf port yet).

I dropped the ball on getting things like this integrated last time, because
I became swamped with personal things unexpectedly.  I will be looking at
making this a bit more uniform--particularly, to do proper a.out/ELF
detection when using config.guess for a native host--and getting those
changes back to the gcc trunk.

-- 
-- Todd Vierling (tv@pobox.com)