Obsoleting more ports for 4.0.

[Joseph S. Myers]

On Tue, 22 Mar 2005, Kazu Hirata wrote:

> > We would like to merge our changes with mainline, 4.0 branch 
> > and the 3.4 branch and continue work in the FSF domain. What 
> > would be the best way to go about this ?
> 
> Send patches to gcc-patches@gcc.gnu.org.  If you are familiar with ARC
> and willing to continue to work on the port, you may want to become a
> maintainer.  That will speed up the process of merging your work into
> the FSF tree.

In addition, run a regression tester which builds unmodified mainline for 
ARC daily or more frequently and runs the GCC testsuites, sends results to 
gcc-testresults and sends differences between daily results to you so you 
can quickly fix or file bugs for regressions that occur.  (If you consider 
4.0 and 3.4 branches of significance for this port, then run regression 
testers on them as well.)  Optionally also send regression reports to the 
people who checked in patches between the runs, but this requires a higher 
degree of reliability of the tester and comparisons and also higher 
frequency to be of enough use.

If a target has a regression tester, or simply an individual doing 
frequent builds, sending results to gcc-testresults on a frequent basis, 
that is an indication that the target is live.  If it doesn't, this 
doesn't itself indicate that the target is dead but may tend to suggest 
that interest in the target is limited.  If you think there is a danger of 
your target being mistaken for dead because of insufficient development 
activity on the GCC lists, keeping testresults going to gcc-testresults 
provides the evidence that the target is not dead after all.

-- 
Joseph S. Myers               http://www.srcf.ucam.org/~jsm28/gcc/
    jsm@polyomino.org.uk (personal mail)
    joseph@codesourcery.com (CodeSourcery mail)
    jsm28@gcc.gnu.org (Bugzilla assignments and CCs)