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: Joel Sherrill <joel dot sherrill at OARcorp dot com>
- To: law at redhat 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 12:06:58 -0500
- Subject: Re: Commit policy wrt. to-be-obsolete targets
- Organization: OAR Corporation
- References: <6964.1022864622@porcupine.cygnus.com>
- Reply-to: joel dot sherrill at OARcorp dot com
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 dejagnu
> > 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'll
> 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?
> jeff
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985