This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Patch commit requirements
- To: Geoff Keating <geoffk at redhat dot com>
- Subject: Re: Patch commit requirements
- From: Toon Moene <toon at moene dot indiv dot nluug dot nl>
- Date: Thu, 21 Jun 2001 21:13:00 +0200
- CC: gcc at gcc dot gnu dot org, jh at suse dot cz, amylaar at redhat dot com, law at cygnus dot com
- Organization: Moene Computational Physics, Maartensdijk, The Netherlands
- References: <200106202042.NAA27914@geoffk.org>
Geoff Keating wrote:
> This is a reminder that generally, before checking in a change, you
> should do all the following:
>
> - Ensure that the tree still bootstraps and all languages test OK.
> - When you post your change (the exact change you plan to commit) to
> gcc-patches, indicate what platform you have used for testing.
Recently, there have been reports of several (i.e. 5) embedded targets
that not even pass a cross-compile bootstrap. Does that mean that we do
not have enough compute cycles to test this every 24 hours (I almost
wrote "night" here, but then I realised that what is `night' to me would
go by another name at the Left Coast of the Pond).
I'm willing to involve super.moene.indiv.nluug.nl for that purpose, but
it requires some work, so I have to be certain this is really necessary.
Cheers,
--
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
Join GNU Fortran 95: http://g95.sourceforge.net/ (under construction)