RE: Target deprecation list

["Nitin Gupta" <ngupta at GlobespanVirata dot com>]

Hi Mark,
	I just figured out sparclet-aout in your deprecation
	list. I missed your first mail, probably it bounced
	from my mail box.	I and "there are 1000 of us using this 
	sparclet-aout port of GCC heavily all day long and we were 
	planning to upgrade to GCC 3.4" :)

	I'm currently upgrading it to GCC 3.2 which I'm almost through. 
	I and our development team here have been eagerly waiting for 
	GCC 3.3 release, with which I'm planning to do regression testing, 
	performance benchmarking of GCC for various implementation of 
	sparclet n/w processors after enabling various new optimizations 
	that come with GCC 3.3; DFA scheduler contributed by Vladimir being 
	the first in pipeline.

	If required, I'm willing to volunteer to maintain this 
	port to keep it alive and evolve with mighty GCC.

Thanks and Regards,
Nitin


> -----Original Message-----
> From: gcc-owner at gcc dot gnu dot org [mailto:gcc-owner at gcc dot gnu dot org]On Behalf Of
> Mark Mitchell
> Sent: Tuesday, April 15, 2003 12:53 PM
> To: gcc at gcc dot gnu dot org
> Subject: Target deprecation list
> 
> 
> 
> A month ago, I posted a list of targets proposed for deprecation:
> 
>   http://gcc.gnu.org/ml/gcc-announce/2003/msg00001.html
> 
> I've received some replies from people who wanted to keep some of the
> targets on that list.  I asked the folks that replied whether they
> were using recent versions of GCC on their target; if they weren't, I
> asked if they planned to do so.  (Some people just want to keep using
> GCC 2.7.3, and they somehow thought we were going to take it away from
> them.)
> 
> Here are the ones we should keep, based on those discussions:
> 
>   arc-*-*
> 
>   hppa*-*-mpeix*
> 
>   i?86-ncr-*
>   i?86-sequent-*
>   i?86-moss-*
>   i?86-*-freebsd2*
>   i?86-*-netbsd*aout*
>   i?86-*-linux*aout*
>   i?86-*-moss*
>   i?86-*-sysv3*
>   i?86-*-interix # not interix3
> 
>   i960-*-*
> 
>   m68000-hp-hpux*
>   m68k-hp-hpux*
> 
>   sparclite-*-coff*
> 
>   vax-*-bsd*        
>   vax-*-netbsd*aout*
>   vax-*-vms*
>   vax-*-sysv*
> 
> That means we can go ahead and lose both the m88k and ROMP targets
> completely, even on the 3.3 branch, if someone is motivated to make
> the changes.
> 
> The other targets that were on the original list, but not on this
> list, can go on the mainline -- but *not* on the 3.3 branch.
> 
> Patches that do nothing but remove obsoleted targets are pre-approved,
> starting in 48 hours so that in case other maintainers and/or the SC
> can remove my pre-approval, if they feel it's inappropriate.
> 
> --
> Mark Mitchell
> CodeSourcery, LLC
> mark at codesourcery dot com
> 
> 


******************Legal Disclaimer**************************
"This email may contain confidential and privileged material for the sole use of the intended recipient.  Any unauthorized review, use or distribution by others is strictly prohibited.  If you have received the message in error, please advise the sender by reply email @globespanvirata.com, and delete the message. Thank you."
****************************************************************