This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Old machine cluster for GCC compile/testing
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Sebastian Pop <sebastian dot pop at cri dot ensmp dot fr>
- Cc: Laurent GUERBY <laurent at guerby dot net>, gcc at gcc dot gnu dot org
- Date: Tue, 9 Aug 2005 21:09:03 -0400 (EDT)
- Subject: Re: Old machine cluster for GCC compile/testing
- References: <1123536063.8058.255.camel@pc.site> <20050809090200.GA2230@napoca.cri.ensmp.fr>
On Tue, 9 Aug 2005, Sebastian Pop wrote:
> Laurent GUERBY wrote:
> >
> > So I'm asking for project proposals, that is to say people that think
> > that their volunteer time to work on these old machine (scripts,
> > compiling, ... under the limit of minimal external bandwidth use) is of
> > some significant benefit to some free software project.
> I'm proposing to automate gcc's bootstrap & regtest: for each mail
> sent to patches@gcc-farm, if 'From' is in gcc-developpers and 'body'
> contains a patch against some branch (ie. if it fails to apply to a
> branch, just drop it and warn the user), enqueue it for validation.
And I'd like to add to that proposal, that the target to test
should be controllable (default "native), to simplify
cross-testing. (Not saying whether it should be possible to
specify multiple targets.)
Perhaps simplest done by using geoffk's script
contrib/regression/btest-gcc.sh, which makes this bit mostly
trivial.
brgds, H-P