This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Sparc bogosity
- From: Geoff Keating <geoffk at geoffk dot org>
- To: lucier at math dot purdue dot edu
- Cc: lucier at math dot purdue dot edu, gcc at gcc dot gnu dot org
- Date: Thu, 31 Jan 2002 20:28:56 -0800
- Subject: Re: Sparc bogosity
- References: <200201312331.g0VNV7d13942@banach.math.purdue.edu>
- Reply-to: Geoff Keating <geoffk at redhat dot com>
> From: Brad Lucier <lucier@math.purdue.edu>
> Date: Thu, 31 Jan 2002 18:31:07 -0500 (EST)
> Cc: lucier@math.purdue.edu, gcc@gcc.gnu.org
> If I wanted to set up your regression tester on one of my sparc servers,
> how would I do it? I searched the gcc web pages without finding many
> operational details about it.
You probably want to look at
<http://people.redhat.com/geoffk/gcc-regression/>. It contains a
complete high-level description of what the tester does.
At present, there are good reasons (most notably, not wanting to
deluge people with mail; but also load on the CVS server) for having
only one regression tester. However, if you have a sufficiently fast
machine you can dedicate to it, I'd be happy to set it up to also run
tests on that machine. In this context, 'sufficiently fast' means
that it can build GCC (in whatever way it should be tested, which
probably means 'configure && make bootstrap && make check') in less
than, say, 2 hours 45 minutes. It might be necessary to occasionally
provide another machine to help people (without sparc machines) debug
any problems that it finds; there's no point reporting problems that
people can't fix.
If you just wanted to run, say, overnight testing, I've just put some
scripts that will help in doing so in CVS (see my other message).
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>