From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23689 invoked by alias); 16 Jan 2002 18:44:55 -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 23585 invoked from network); 16 Jan 2002 18:44:52 -0000 Received: from unknown (HELO gandalf.codesourcery.com) (66.60.148.227) by sources.redhat.com with SMTP; 16 Jan 2002 18:44:52 -0000 Received: from gandalf.codesourcery.com (localhost.localdomain [127.0.0.1]) by gandalf.codesourcery.com (8.11.6/8.11.6) with ESMTP id g0GAiqk01876; Wed, 16 Jan 2002 02:44:52 -0800 Date: Wed, 16 Jan 2002 11:18:00 -0000 From: Mark Mitchell To: "Bradley D. LaRonde" , "gcc@gcc.gnu.org" Subject: Re: Plans for 3.0.4 ? Message-ID: <5840000.1011177892@gandalf.codesourcery.com> In-Reply-To: <055a01c19eaf$889a6610$5601010a@prefect> X-Mailer: Mulberry/2.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-SW-Source: 2002-01/txt/msg01153.txt.bz2 > In my case, 3.0.2 worked fine (for me, ymmv), 3.0.3 introduced the -mtune > brokenness, and the 3.0 branch remains broken to the best of my knowledge. > I flagged the problem the arch maintainer Eric Christopher. Maybe I > should file a formal bug report? Or produce a patch, or contact the person who introduced the regression and ask them to fix it. The point is that I am happy to coordinate a 3.0.4 release -- but I cannot fix all the bugs that might be out there. :-( Let's follow the following procedure: 1. If you would like to see a 3.0.4 release, please send me mail privately. Explain what bugs have already been fixed on the branch that are important to you. 2. If there are bugs that have not already been fixed, but which are regressions in 3.0.3 relative to previous releases, please file GNATS bug reports, and send me the PR number with your mail. I will then coordinate this information and get a release out. Yours, -- Mark Mitchell mark@codesourcery.com CodeSourcery, LLC http://www.codesourcery.com