From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24690 invoked by alias); 28 Sep 2009 15:38:32 -0000 Received: (qmail 24680 invoked by uid 22791); 28 Sep 2009 15:38:30 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 28 Sep 2009 15:38:26 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 78CEF2BAAD7; Mon, 28 Sep 2009 11:38:24 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id hgjzLGVFz9zV; Mon, 28 Sep 2009 11:38:24 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 317AF2BAAE3; Mon, 28 Sep 2009 11:38:24 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id A1107F593C; Mon, 28 Sep 2009 08:38:18 -0700 (PDT) Date: Mon, 28 Sep 2009 15:38:00 -0000 From: Joel Brobecker To: Ulrich Weigand Cc: gdb@sourceware.org Subject: Re: GDB 7.0 regressions: s390(x)-linux, ppc(64)-linux, spu-elf Message-ID: <20090928153818.GE9019@adacore.com> References: <200909272155.n8RLt01J002128@d12av02.megacenter.de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909272155.n8RLt01J002128@d12av02.megacenter.de.ibm.com> User-Agent: Mutt/1.5.18 (2008-05-17) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00310.txt.bz2 > I've now analyzed the GDB test suite for regressions on the platforms > I'm most interested in: s390(x)-linux, ppc(64)-linux, and spu-elf. > Unfortunately, this did show up a number of real regressions as > compared to the last release. :-(. Thanks for the heads up. > How should we proceed with these issues? Should I commit the fixes > to the branch? What's the deadline? The target date for release is Wed, so we're about 48 hours away. If you feel confident about your fix, then you should go ahead and commit to the branch. According to the guidelines I remember reading somewhere (it might be in the MAINTAINERS file), if the change only affects one target, we can also discuss putting that change in. For the rest of your patches, we need to look at them individually and evaluate the risk. Based on that, we can decide whether delaying the release is necessary, and whether each patch should be applied to the branch and if yes, whether it should be applied now (for 7.0), or only after it has had a chance to be tested a little more on the HEAD. -- Joel