From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30757 invoked by alias); 28 Apr 2003 06:03:13 -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 30750 invoked from network); 28 Apr 2003 06:03:12 -0000 Received: from unknown (HELO doubledemon.codesourcery.com) (66.60.148.227) by sources.redhat.com with SMTP; 28 Apr 2003 06:03:12 -0000 Received: from doubledemon.codesourcery.com (doubledemon.codesourcery.com [127.0.0.1]) by doubledemon.codesourcery.com (8.12.8/8.12.8) with ESMTP id h3S63B9X008462; Sun, 27 Apr 2003 23:03:12 -0700 Subject: RE: GCC 3.3 Status From: Mark Mitchell To: "S. Bosscher" Cc: "'gcc@gcc.gnu.org '" In-Reply-To: <4195D82C2DB1D211B9910008C7C9B06F01F3732B@lr0nt3.lr.tudelft.nl> References: <4195D82C2DB1D211B9910008C7C9B06F01F3732B@lr0nt3.lr.tudelft.nl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 28 Apr 2003 08:14:00 -0000 Message-Id: <1051509792.8310.22.camel@doubledemon.codesourcery.com> Mime-Version: 1.0 X-SW-Source: 2003-04/txt/msg01393.txt.bz2 On Tue, 2003-04-22 at 16:14, S. Bosscher wrote: > Mark, > > You already have downgraded quite a few PRs, and now you're about to > downgrade a few more. I think that for 3.3 it is the right decision (heck, > it's got to go out now, can't wait forever), but is it your intention to > upgrade those PRs again once 3.3 is released? For most of them, I'm just taking the 3.3 out of the synopsis; that pushes them into the 3.4 list. For something like "unclear error message", I might downgrade the PR to medium priority; I'm not sure that we'd ever hold up a release for that. > Many PRs against 3.3 have been simply ignored, or were not recognised as > regressions, for some time (until Wolfgang started his Great Work of > analysing all those PRs). Most of them are still present on the trunk. And > they _are_ regressions, even if everybody agrees that they should not hold > up 3.3 any longer. Yes, Wolfgang's contribution has been massive. Truly outstanding. And yes, we need to try to fix more of these for 3.4. -- Mark Mitchell CodeSourcery, LLC mark@codesourcery.com