From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25300 invoked by alias); 5 Dec 2001 18:17:09 -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 25234 invoked from network); 5 Dec 2001 18:16:58 -0000 Received: from unknown (HELO e21.nc.us.ibm.com) (32.97.136.227) by sources.redhat.com with SMTP; 5 Dec 2001 18:16:58 -0000 Received: from southrelay03.raleigh.ibm.com (southrelay03.raleigh.ibm.com [9.37.3.210]) by e21.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id MAA127334; Wed, 5 Dec 2001 12:13:28 -0600 Received: from gateway1.beaverton.ibm.com (gateway1.beaverton.ibm.com [138.95.180.2]) by southrelay03.raleigh.ibm.com (8.11.1m3/NCO v5.01) with ESMTP id fB5IGg7147166; Wed, 5 Dec 2001 13:16:42 -0500 Received: from eng2.beaverton.ibm.com (eng2.beaverton.ibm.com [138.95.200.91]) by gateway1.beaverton.ibm.com (8.11.2/8.11.2) with ESMTP id fB5IGbo01169; Wed, 5 Dec 2001 10:16:37 -0800 Received: from dyn9-47-18-192.des.beaverton.ibm.com (dyn9-47-18-192.des.beaverton.ibm.com [9.47.18.192]) by eng2.beaverton.ibm.com (8.10.0.Beta10/8.8.5/token.aware-1.2) with ESMTP id fB5IGaQ04126; Wed, 5 Dec 2001 10:16:36 -0800 (PST) Received: (from janis@localhost) by dyn9-47-18-192.des.beaverton.ibm.com (8.9.3/8.9.3) id KAA01978; Wed, 5 Dec 2001 10:19:54 -0800 Date: Wed, 05 Dec 2001 10:17:00 -0000 From: Janis Johnson To: Joe Buck Cc: Janis Johnson , gcc@gcc.gnu.org Subject: Re: build status page problem Message-ID: <20011205101954.A1968@us.ibm.com> References: <200112051801.KAA21064@atrus.synopsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200112051801.KAA21064@atrus.synopsys.com>; from jbuck@synopsys.com on Wed, Dec 05, 2001 at 10:01:26AM -0800 X-SW-Source: 2001-12/txt/msg00225.txt.bz2 On Wed, Dec 05, 2001 at 10:01:26AM -0800, Joe Buck wrote: > I have an issue with > > http://gcc.gnu.org/gcc-3.0/buildstat.html. > > No distinction is made between 3.0, 3.0.1, and 3.0.2, and it's possible > that an unnoticed regression might mean that, say, 3.0.1 builds on some > obscure platform but 3.0.2 does not. We need to include the actual > release number, there is no such thing as "3.0.x". > The assumption is that everything on the GCC 3.0 build status page builds with all releases of 3.0.x unless it says otherwise. So far there's only one note otherwise, for s390-linux-gnu which is supported beginning with 3.0.1. I'd prefer to keep that assumption. If there's a regression that prevents a target from building with a particular release we can add a note to that effect for that target. Janis