This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Beyond GCC 3.0: Summing Up
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: Beyond GCC 3.0: Summing Up
- From: Richard Earnshaw <rearnsha at arm dot com>
- Date: Tue, 10 Jul 2001 18:51:44 +0100
- cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Richard dot Earnshaw at arm dot com
- Organization: ARM Ltd.
- Reply-To: Richard dot Earnshaw at arm dot com
> However, that decision should be made independently. If a patch breaks
> ROMP, we should ask if we still want to support it. If
> we don't, then we don't care, and that failure is not a regression;
> the spec has changed. Ideally, we would decide what platforms,
> if any, to obsolete at the *start* of a major release cycle,
> and then make the remainder work well. It seems a bit odd to
> decide in the middle of things to desupport a target because some
> patch breaks it, but seems otherwise good.
And, ideally, such decisions should be made public (either by posting to
gcc-announce, or by a statement in the release notes of a preceding
release). Then someone who really needs such support has the opportunity
to step forward with either time or money as the case may be.
R.