From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8125 invoked by alias); 14 Oct 2004 12:04:58 -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 8107 invoked from network); 14 Oct 2004 12:04:52 -0000 Received: from unknown (HELO smtp10.atl.mindspring.net) (207.69.200.246) by sourceware.org with SMTP; 14 Oct 2004 12:04:52 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp10.atl.mindspring.net with esmtp (Exim 3.33 #1) id 1CI4Li-0005ZN-00; Thu, 14 Oct 2004 08:04:50 -0400 Received: from mindspring.com (localhost [127.0.0.1]) by berman.michael-chastain.com (Postfix) with SMTP id C810B4B359; Thu, 14 Oct 2004 08:05:35 -0400 (EDT) Date: Thu, 14 Oct 2004 12:04:00 -0000 From: Michael Chastain To: zack@codesourcery.com, gdb-patches@sources.redhat.com Subject: Re: testsuite fixes for bleeding edge gcc Message-ID: <416E6B8F.nail1FK2IQHOI@mindspring.com> References: <87brf5n3c4.fsf@codesourcery.com> In-Reply-To: <87brf5n3c4.fsf@codesourcery.com> User-Agent: nail 10.8 6/28/04 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-10/txt/msg00243.txt.bz2 Hi Zack! > Current development versions of GCC are substantially pickier about > "built-in" library functions being properly declared, which causes a > large number of GDB testsuite failures. Yes. > 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. Michael