From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19143 invoked by alias); 31 Jan 2003 11:03:42 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 19136 invoked from network); 31 Jan 2003 11:03:42 -0000 Received: from unknown (HELO gold.csi.cam.ac.uk) (131.111.8.12) by 172.16.49.205 with SMTP; 31 Jan 2003 11:03:42 -0000 Received: from student.cusu.cam.ac.uk ([131.111.179.82] helo=kern.srcf.societies.cam.ac.uk ident=mail) by gold.csi.cam.ac.uk with esmtp (Exim 4.10) id 18eYxR-0005s1-00; Fri, 31 Jan 2003 11:03:41 +0000 Received: from jsm28 (helo=localhost) by kern.srcf.societies.cam.ac.uk with local-esmtp (Exim 3.35 #1 (Debian)) id 18eYxR-0005mC-00; Fri, 31 Jan 2003 11:03:41 +0000 Date: Fri, 31 Jan 2003 13:50:00 -0000 From: "Joseph S. Myers" X-X-Sender: To: Benjamin Kosnik cc: , Subject: Re: GCC 3.3, GCC 3.4 In-Reply-To: <20030130181313.7d3c5820.bkoz@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-01/txt/msg01751.txt.bz2 On Thu, 30 Jan 2003, Benjamin Kosnik wrote: > I think the longer gcc, as a project, goes on without an autobuild > continuous regression checker, the worse off things will get. It was > nice of Red Hat to initially support this effort, but it is obvious that > this time is past as the regression checker is long dead. Somebody else > will have to step up with the bandwidth, time, and machine to do this. The one that Geoff was running at Red Hat is now running at Apple (Darwin native only, rather than one native and two cross). I think there's also a separate one running on athlon_mp-pc-linux-gnu (look for Autocrasher in the gcc-regression archives). However, we do need a simple system for anyone (with a fast enough system) to be able to set up the tester and run it, and have the results all go into a single mail if they arrive in time (to avoid twenty mails going out whenever the tree is broken). All primary platforms should be covered, and any secondary platforms or crosses with simulators available that someone wants to run the tester for. Also testers running on release branches would be useful. And I think development policies need to be changed to freeze the tree if a regression persists for more than a few days; too often the old tester had regressions persisting, unfixed, for a month or more. -- Joseph S. Myers jsm28@cam.ac.uk