From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28313 invoked by alias); 14 Oct 2004 16:59:25 -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 28306 invoked from network); 14 Oct 2004 16:59:24 -0000 Received: from unknown (HELO mail.codesourcery.com) (65.74.133.9) by sourceware.org with SMTP; 14 Oct 2004 16:59:24 -0000 Received: (qmail 13331 invoked from network); 14 Oct 2004 16:59:24 -0000 Received: from taltos.codesourcery.com (zack@66.92.218.83) by mail.codesourcery.com with DES-CBC3-SHA encrypted SMTP; 14 Oct 2004 16:59:24 -0000 Received: by taltos.codesourcery.com (sSMTP sendmail emulation); Thu, 14 Oct 2004 09:59:23 -0700 To: Michael Chastain Cc: gdb-patches@sources.redhat.com Subject: Re: testsuite fixes for bleeding edge gcc References: <87brf5n3c4.fsf@codesourcery.com> <416E6B8F.nail1FK2IQHOI@mindspring.com> From: Zack Weinberg Date: Thu, 14 Oct 2004 16:59:00 -0000 In-Reply-To: <416E6B8F.nail1FK2IQHOI@mindspring.com> (Michael Chastain's message of "Thu, 14 Oct 2004 08:05:35 -0400") Message-ID: <87y8i9kzh0.fsf@codesourcery.com> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-10/txt/msg00248.txt.bz2 Michael Chastain writes: >> The appended patch adds all the missing declarations to the 6.2-branch >> version of the testsuite. I haven't tried mainline. Thoughts? > > Except for gdb.mi/gdb701, these are all fixed in gdb HEAD. > Also fixed in gdb HEAD are gdb.thread/*.exp, plus two tests > that check the gcc version number that needed 'gcc-4-*'. > > gdb_6_2-branch is dead. Andrew is going to create gdb_6_3-branch > in a few more days or so. > > If you really do have a need for it, I could merge the whole test suite > from HEAD to gdb_6_2-branch. I stopped testing gdb_6_2-branch just > recently, but before I stopped, I was regularly testing gdb from the > branch with the test suite from gdb HEAD. I was only testing gdb_6_2-branch because I wanted to avoid hypothetical breakage in gdb HEAD which would confuse the issue of whether my GCC changes worked. If y'all are about to branch for a 6.3 release, perhaps I do not need to be doing that right now. Would be nice to get gdb.mi/gdb701 fixed in HEAD though. zw