This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] config.gcc: Obsolete c4x.
- From: Kazu Hirata <kazu at cs dot umass dot edu>
- To: mark at codesourcery dot com
- Cc: zack at codesourcery dot com, ralf dot corsepius at rtems dot org, joel dot sherrill at OARcorp dot com, gcc-patches at gcc dot gnu dot org, m dot hayes at elec dot canterbury dot ac dot nz, Svein at dev dot seldal dot com
- Date: Thu, 05 May 2005 08:12:01 -0400 (EDT)
- Subject: Re: [patch] config.gcc: Obsolete c4x.
- References: <4278F97D.9050905@codesourcery.com><87hdhiew2j.fsf@codesourcery.com><42792986.6050803@codesourcery.com>
Hi Mark,
> Kazu, let's make Ralf and Joel happy, and make this a somewhat more
> gentle transition. Would you please add the bits back to the 4.0
> branch? At the same time, add c4x to the list of obsolete targets, so
> that --enable-obsolete is required to actually build it. Let's leave
> the mainline alone; if someone actually does come forward to maintain
> the port, we can resurrect it.
All I have done so far is touch --enable-obsolete. I have not removed
any file.
c4x has been added to the list of obsolete targets on the web site as
well as config.gcc on both 4.0 branch (but not 4.0.0) and mainline.
Should I remove the config.gcc bits on mainline? I think
--enable-obsolete is a fairly low hurdle, but if you think otherwise,
I'm going to not require --enable-obsolete for c4x on mainline.
Kazu Hirata