This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PROPOSAL: Policy for obsoleting targets
- From: Joe Buck <jbuck at synopsys dot com>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 16 May 2003 09:34:57 -0700
- Subject: Re: PROPOSAL: Policy for obsoleting targets
- References: <874r3u27sm.fsf@egil.codesourcery.com>
> In the future I would like to do this more objectively. To that end I
> am proposing:
>
> At the time GCC version 3.n is released, all targets which have not
> had a successful build and test report posted to gcc-testresults
> for prereleases of minor version n, or releases n-1 and n-2, go on
> the obsoletion list for version n+1. "Successful" means minimum
> useful functionality: it's okay if only the C compiler works.
I'd have an issue with that, because there are many targets in active
use that we never seem to get any reports for. The Debian folks are the
biggest example: they maintain about 11 different platforms and do
detailed bug tracking, yet we rarely get any reports from them.
In many cases they appear to do their own patches, if we break some port.
Now, I suppose if you want to threaten the Debian people with the loss of
their platforms, they might actually send us success reports. But is that
the way we want to play?