From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31301 invoked by alias); 31 Jan 2003 19:05:26 -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 31292 invoked from network); 31 Jan 2003 19:05:25 -0000 Received: from unknown (HELO localhost.localdomain) (66.60.148.227) by 172.16.49.205 with SMTP; 31 Jan 2003 19:05:25 -0000 Received: from warlock.codesourcery.com (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.11.6/8.11.6) with ESMTP id h0VJ1WC01913; Fri, 31 Jan 2003 11:01:32 -0800 Date: Fri, 31 Jan 2003 20:23:00 -0000 From: Mark Mitchell To: Matt Austern cc: "Joseph S. Myers" , Benjamin Kosnik , "gcc@gcc.gnu.org" Subject: Re: GCC 3.3, GCC 3.4 Message-ID: <59050000.1044039692@warlock.codesourcery.com> In-Reply-To: <221AE814-354D-11D7-A302-00039390D9E0@apple.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-SW-Source: 2003-01/txt/msg01797.txt.bz2 --On Friday, January 31, 2003 10:52:23 AM -0800 Matt Austern wrote: > On Friday, January 31, 2003, at 08:48 AM, Mark Mitchell wrote: > >> Nobody seems to be objecting particularly much to the idea of leaving >> stage 1 for GCC 3.4 on March 15th. So, let's make that firm. We've >> already got two major pieces of new technology: a new C++ parser, and >> PCH support. > > I have two concerns about the March 15 deadline. > > First, a technical concern: people have also been talking about putting > the new register allocator into 3.4. I'd like to see that as a third > major piece of new technology, which would imply a later deadline. What's the prognosis for the register allocator? When will it be ready to check in, and when will the bugs be out? (I consider the C++ parser to still be too buggy to release, even though it works well for most code. It passed the tests, which got it into the tree, but people have certainly been finding problems.) > Second, a process concern: March 15 for the end of 3.4 phase 1 is > awfully close to the 3.3 code freeze. I don't think we can worry about this much, since we don't really know when the 3.3 freeze is going to be. There's not a whole lot of support for doing a 3.3 release at all; at this point, I think we should see how 3.3 develops before worrying about it too much. -- Mark Mitchell mark@codesourcery.com CodeSourcery, LLC http://www.codesourcery.com