From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19506 invoked by alias); 21 Sep 2009 18:23:24 -0000 Received: (qmail 19497 invoked by uid 22791); 21 Sep 2009 18:23:23 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 21 Sep 2009 18:23:18 +0000 Received: from zps38.corp.google.com (zps38.corp.google.com [172.25.146.38]) by smtp-out.google.com with ESMTP id n8LINEpY021597 for ; Mon, 21 Sep 2009 19:23:15 +0100 Received: from pzk41 (pzk41.prod.google.com [10.243.19.169]) by zps38.corp.google.com with ESMTP id n8LIMCT3004323 for ; Mon, 21 Sep 2009 11:23:12 -0700 Received: by pzk41 with SMTP id 41so268754pzk.0 for ; Mon, 21 Sep 2009 11:23:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.67.5 with SMTP id p5mr305083wfa.286.1253557391473; Mon, 21 Sep 2009 11:23:11 -0700 (PDT) In-Reply-To: References: <4AB58A42.7030801@gmail.com> Date: Mon, 21 Sep 2009 18:23:00 -0000 Message-ID: Subject: Re: GCC 4.5 Status Report (2009-09-19) From: Cary Coutant To: Richard Guenther Cc: gcc@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-09/txt/msg00412.txt.bz2 >> =A0 So aren't we now likely to lose the first few days of what little re= mains of >> stage 1 waiting for trunk to start working again, then have a mad rush of >> people falling all over each other to get their new features in in the l= ast >> couple of days? =A0One of which will inevitably break trunk again and bl= ock all >> the others and then stage 1 will be over and it'll all be too late? > > I am not aware of any big patches that are still pending. =A0Coming up > with new yet unknown things now wouldn't be a good timing anyway. I was hoping to get the dwarf4 branch merged into trunk during stage 1. While it's not a small patch, it's also not really that intrusive in that it consists mostly of new code that runs only with the -gdwarf-4 option. I've been testing it on a lot of big code bases for the last few months, and haven't found any new bugs for a more than a month now, so I think it's ready. I'll work on merging top-of-trunk into the branch early this week and then send a patch to merge back into the trunk. -cary