From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-67173-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 28903 invoked by alias); 30 Jan 2003 18:04:18 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 28893 invoked from network); 30 Jan 2003 18:04:11 -0000
Received: from unknown (HELO mail-out1.apple.com) (17.254.0.52)
  by 172.16.49.205 with SMTP; 30 Jan 2003 18:04:11 -0000
Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225])
	by mail-out1.apple.com (8.11.3/8.11.3) with ESMTP id h0UI4Aw14484
	for <gcc@gcc.gnu.org>; Thu, 30 Jan 2003 10:04:10 -0800 (PST)
Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T601af3dea9118064e13c4@mailgate1.apple.com>;
 Thu, 30 Jan 2003 10:04:10 -0800
Received: from apple.com (mrs1.apple.com [17.201.24.248])
	by scv3.apple.com (8.11.3/8.11.3) with ESMTP id h0UI49f27410;
	Thu, 30 Jan 2003 10:04:09 -0800 (PST)
Date: Thu, 30 Jan 2003 19:07:00 -0000
Subject: Re: GCC 3.3, GCC 3.4
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
Cc: gcc@gcc.gnu.org
To: mark@codesourcery.com
From: Mike Stump <mstump@apple.com>
In-Reply-To: <200301300728.h0U7ShQ31506@localhost.localdomain>
Message-Id: <D9D52B3D-347C-11D7-8309-003065A77310@apple.com>
Content-Transfer-Encoding: 7bit
X-SW-Source: 2003-01/txt/msg01654.txt.bz2

On Wednesday, January 29, 2003, at 11:28 PM, Mark Mitchell wrote:
> I would like to release GCC 3.3 on March 1.

> I'll start banging on GCC 3.3 regressions, and encouraging others to
> do the same.

Matt will bring up the issue of compile time regressions...  :-)  To 
that end, I'd like to ask if I can move the regclass change from 
mainline to 3.3.  While _it_ specifically didn't regress, it helps hide 
the other, real regressions.  Those should be fixed as well...