From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18543 invoked by alias); 13 Oct 2006 16:34:05 -0000 Received: (qmail 18535 invoked by uid 22791); 13 Oct 2006 16:34:04 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 13 Oct 2006 16:33:58 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 8418248CF92; Fri, 13 Oct 2006 12:33:53 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20748-01-8; Fri, 13 Oct 2006 12:33:53 -0400 (EDT) Received: from takamaka.act-europe.fr (unknown [70.71.0.212]) by nile.gnat.com (Postfix) with ESMTP id F3A2D48CDAA; Fri, 13 Oct 2006 12:33:52 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 1BAF447F00; Fri, 13 Oct 2006 09:33:52 -0700 (PDT) Date: Fri, 13 Oct 2006 16:34:00 -0000 From: Joel Brobecker To: Nick Roberts , gdb-patches@sources.redhat.com Subject: Re: arrayidx.exp failures Message-ID: <20061013163352.GJ1059@adacore.com> References: <17710.63085.830960.73093@kahikatea.snap.net.nz> <20061013023839.GI1059@adacore.com> <20061013043855.GA28303@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061013043855.GA28303@nevyn.them.org> User-Agent: Mutt/1.4i Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00155.txt.bz2 > FYI, Joel, I have no idea what compilers you test with - but half of > the Ada tests in the GDB testsuite have never passed for me with FSF > gnat, at least 4.0 and 4.1, and possibly 3.4 too. It's good you told me, I will try to talk to some of my collegues who work on the compiler and see where we are. I use exclusively GNAT Pro, which is the compiler we maintain at AdaCore. Right now, it's based on GCC 3.4.6, but are actively moving to a GCC 4.1 backend on most of our platforms. That's when we found a lot of issues in debug info generation that apparently appear only with Ada - we have fixed several of them and I believe that they have been submitted although I will admit that I do not follow compiler work very closely. If I started doing my testing with various flavours of GCC, the number of combinations would explode. I already run our in-house testsuite (not based on dejagnu) together with the GDB testsuite, both with our GDB tree and the FSF head. All I can say is that we're getting better at pushing our changes to the FSF tree both on the GCC side as well as the GDB side, but it's a slow process because first we have to catch up and then we have to learn how to best do it. In the meantime, are these fails an issue? For me, I have the same sort of issue in a smaller scale with C++ testcases, but the way I test is by using a smart-diff between the testcase results before and after. -- Joel