From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32034 invoked by alias); 13 Dec 2005 19:08:12 -0000 Received: (qmail 32019 invoked by uid 48); 13 Dec 2005 19:08:09 -0000 Date: Tue, 13 Dec 2005 19:08:00 -0000 Message-ID: <20051213190809.32018.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug testsuite/25352] xfail within dg-do command has no effect In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "janis at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2005-12/txt/msg01365.txt.bz2 List-Id: ------- Comment #4 from janis at gcc dot gnu dot org 2005-12-13 19:08 ------- xfail within a dg-do command other than run has no effect, at least not with DejaGnu 1.4.4 used with GCC at least as far back as 3.0. The DejaGnu documentation doesn't mention the dg-* directives. The comments in dejagnu/dg.exp file implies that xfail should be recognized for all dg-do options. There are 50+ tests in gcc/testsuite that use xfail with dg-do assemble, compile, and link, so perhaps it worked at one time. The generated tests in gcc/testsuite/gcc.test-framework only test xfail with "dg-do run", and there are no permanent tests for xfail with dg-do and other actions. There's undoubtedly a way for the GCC dg scripts to capture the information that the test's dg-do had an xfail, although it will probably be ugly. I'll keep investigating to find out just how ugly it will need to be. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25352