This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Commit policy wrt. to-be-obsolete targets
- From: law at redhat dot com
- To: joel dot sherrill at OARcorp dot com
- Cc: Jason R Thorpe <thorpej at wasabisystems dot com>, Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, Zack Weinberg <zack at codesourcery dot com>, gcc at gcc dot gnu dot org
- Date: Fri, 31 May 2002 11:32:37 -0600
- Subject: Re: Commit policy wrt. to-be-obsolete targets
- Reply-to: law at redhat dot com
In message <3CF7ADB2.5FC28447@OARcorp.com>, Joel Sherrill writes:
> law@redhat.com wrote:
> >
> > In message <20020531080027.P523@dr-evil.shagadelic.org>, Jason R Thorpe
> > writes:
> > > I know there are some codegen bugs lurking, but a mostly-working
> > NetBSD/pc532
> > > kernel can be built from the current compiler. We're working on a deja
> gnu
> > > setup so we can do the execute bits of the testsuite in some reasonable
> > > manner (I have to figure out how to make dejagnu do the execute tests
> > > remotely -- you do NOT want to know how long it takes a pc532 to build
> tcl :
> > It certainly has these kinds of capabilities. You should be able to build
> > the tests on a modern host and run the testsuite on the modern host. It'l
> l
> > arrange to push the binaries down to the target machine via ssh, nfs, rcp,
> etc
> > [ I don't recall precisely which transports are currently used. ]
>
> If Jason is willing to fix, regularly test, and report on the
> pc532 does this mean the target should not be obsoleted at this
> time?
Between Jason and Ian, if one or both of them are willing to take up this
task, then we should not obsolete the port IMHO.
jeff