From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13474 invoked by alias); 18 Sep 2003 16:05:01 -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 13464 invoked from network); 18 Sep 2003 16:05:00 -0000 Received: from unknown (HELO hawaii.kealia.com) (209.3.10.89) by sources.redhat.com with SMTP; 18 Sep 2003 16:05:00 -0000 Received: by hawaii.kealia.com (Postfix, from userid 2049) id 31633CB26; Thu, 18 Sep 2003 09:05:00 -0700 (PDT) To: Andrew Cagney Cc: Michael Elizabeth Chastain , gdb-patches@sources.redhat.com Subject: Re: [testsuite] add gdb.cp/gdb1355.exp References: <200309180201.h8I21hCr013787@duracef.shout.net> <3F69C0C0.8070009@redhat.com> From: David Carlton Date: Thu, 18 Sep 2003 16:05:00 -0000 In-Reply-To: <3F69C0C0.8070009@redhat.com> (Andrew Cagney's message of "Thu, 18 Sep 2003 10:27:12 -0400") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-09/txt/msg00397.txt.bz2 On Thu, 18 Sep 2003 10:27:12 -0400, Andrew Cagney said: > I also intend again proposing that existing XFAILS get yanked. That sounds okay to me. I just scanned the XFAILS in gdb.cp; there's a lot of HP-specific stuff that we have no reason to believe is accurate, and a lot of branches that are XFAILed for everybody without any comments as to when we expect that output. I don't see how either of those situations are helping us at all. There are a few XFAILS which have a bug number associated with them that's around 2400 or so: these are especially urgent, because it won't be all _that_ long before the bug number might start looking like a GDB bug number. The one that looked at first blush like it might be reasonable is the 'setup_xfail_format "stabs"' in method.exp; and, indeed it is triggered with GCC 2.95.3, but not with GCC 3.2 (even when using stabs). In fact, no XFAILS are triggered anywhere in gdb.cp with GCC 3.2 (on i686-pc-linux-gnu, GCC 3.2, DWARF 2 or stabs); on GCC 2.95.3, I see these: XFAIL: gdb.cp/classes.exp: ptype class vB (FIXME: non-portable virtual table constructs) XFAIL: gdb.cp/classes.exp: ptype class vC (FIXME: non-portable virtual table constructs) XFAIL: gdb.cp/classes.exp: ptype class vD (FIXME: non-portable virtual table constructs) XFAIL: gdb.cp/classes.exp: ptype class vE (FIXME: non-portable virtual table constructs) XFAIL: gdb.cp/method.exp: print this in A::bar (missing const) where the last one is the one I referred to above, and it's not at all clear from the other 4 whether they really should be XFAILs or KFAILs (does the FIXME refer to GDB or GCC?). So, if the state of XFAILs in other subdirectories of testsuite is like that for gdb.cp, I don't think they're doing us any good. David Carlton carlton@kealia.com