From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27259 invoked by alias); 30 Apr 2012 18:52:31 -0000 Received: (qmail 27247 invoked by uid 22791); 30 Apr 2012 18:52:29 -0000 X-SWARE-Spam-Status: No, hits=-3.4 required=5.0 tests=BAYES_00,KHOP_THREADED,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from usmamail.tilera.com (HELO USMAMAIL.TILERA.COM) (12.216.194.151) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 30 Apr 2012 18:51:59 +0000 Received: from [10.7.0.51] (10.9.0.23) by USMAExch2.tad.internal.tilera.com (10.3.0.33) with Microsoft SMTP Server id 14.0.694.0; Mon, 30 Apr 2012 14:51:58 -0400 Message-ID: <4F9EDF47.1080904@tilera.com> Date: Mon, 30 Apr 2012 19:06:00 -0000 From: Jeff Kenton User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2 MIME-Version: 1.0 To: Pedro Alves CC: Yao Qi , Subject: Re: [PATCH] Add support for Tilera TILE-Gx processor (part 2/2: gdb) References: <4F9066C5.30501@tilera.com> <4F917C1F.3060804@codesourcery.com> <4F917F7F.9030601@tilera.com> <4F9EDD4B.3020409@redhat.com> In-Reply-To: <4F9EDD4B.3020409@redhat.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-04/txt/msg01086.txt.bz2 On 04/30/2012 02:43 PM, Pedro Alves wrote: > I meant to reply to this before, but it slipped... > > On 04/20/2012 04:23 PM, Jeff Kenton wrote: > > === gdb Summary === > > # of expected passes 18181 > # of unexpected failures 625 > > Did you look at what is causing these hundreds of failures? Although there > are thousands of passes, such high failure rate is usually indicative of > something badly borked. You'd be surprised at how far in testsuite results > you can get with a gdb that manages to loads programs, but is a brick > at actually debugging live programs ... > >> # of expected failures 100 >> # of known failures 59 >> # of untested testcases 12 >> # of unresolved testcases 4 >> # of unsupported tests 118 >> /gdb_tests/gdb/build/gdb/testsuite/../../gdb/gdb version 7.4.50.20120410 -nw -nx -data-directory /gdb_tests/gdb/build/gdb/testsuite/../data-directory > We use it on production systems, so lots of things work. Checking the failures is on my list of things to do. Is there a target failure threshhold we need to hit before our GDB is accepted, or can we submit what we have (with the fixes you specified) and work on the remaining test suite failures afterwards? --jeff kenton