From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31354 invoked by alias); 2 Apr 2002 04:49:06 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 31341 invoked from network); 2 Apr 2002 04:49:04 -0000 Received: from unknown (HELO is.elta.co.il) (199.203.121.2) by sources.redhat.com with SMTP; 2 Apr 2002 04:49:04 -0000 Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id HAA29780; Tue, 2 Apr 2002 07:47:45 +0200 (IST) Date: Mon, 01 Apr 2002 20:49:00 -0000 From: Eli Zaretskii X-Sender: eliz@is To: Michael Elizabeth Chastain cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] import drow dbxread.c fix to branch In-Reply-To: <200204011922.g31JMnt20803@duracef.shout.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-04/txt/msg00014.txt.bz2 On Mon, 1 Apr 2002, Michael Elizabeth Chastain wrote: > My test bed loves it for 5.2 (linux native). It improves gcc 2.95.3 > -gstabs+ and has no change with any other gcc/goption combination. > > Okay to import into 5.2? Can you please post a simple test program, and a procedure to test the relevant feature before and after the patch? (I cannot run the test suite on my system.) In general, I think only safe fixes for grave bugs should go into the branch. If we still have problems for which such solutions are impossible, but which are deemed too grave to not solve them in 5.2, it would mean that the branch was cut too early, and we should consider canceling the branch and starting the release cycle anew.