This is the mail archive of the
mailing list for the GCC project.
Re: m68k target deprecations
- From: Bernardo Innocenti <bernie at develer dot com>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org, Richard Henderson <rth at redhat dot com>, Andreas Schwab <schwab at suse dot de>,Gunther Nikl <gni at gecko dot de>
- Date: Sat, 13 Sep 2003 18:34:34 +0200
- Subject: Re: m68k target deprecations
- Organization: Develer S.r.l.
- References: <3F60EC0A.firstname.lastname@example.org> <email@example.com>
Zack Weinberg wrote:
is it still possible to add new entries in the (now empty)
list of obsolete targets for the upcoming 3.4?
I am not sure I understand your question. No more targets are going
to be removed entirely from the 3.4 release series. However, we will
as usual come up with a list of targets to be marked obsoleted in 3.4
and removed from the mainline after 3.4 branches.
This is exactly what I was meaning.
I certainly intend to target the m68k architecture for aggressive
removal of dead targets.
Shouldn't that be done way before entering stage 3? We've got less
than one month left to discuss the topic. And I suppose such
arguments can easily degenerate into endless flamewars :-)
I am hoping to come up with objective criteria for declaring targets
obsolete, which will reduce the amount of arguing involved in the
What about including all targets that nobody is volunteering
to maintain and/or have been broken for some time?
// Bernardo Innocenti - Develer S.r.l., R&D dept.
Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html