From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8369 invoked by alias); 12 Dec 2005 17:57:57 -0000 Received: (qmail 8355 invoked by uid 48); 12 Dec 2005 17:57:55 -0000 Date: Mon, 12 Dec 2005 17:57:00 -0000 Message-ID: <20051212175755.8354.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/msg01195.txt.bz2 List-Id: ------- Comment #2 from janis at gcc dot gnu dot org 2005-12-12 17:57 ------- This is odd, if the test case has a syntax error the xfail works as expected, but with #error it doesn't. I'll look into it. Take a look at gcc/testsuite/gcc.test-framework, which tests lots of combinations of directives as well as specific cases. I run it as part of my nightly build of trunk. It's meant to be run separately from the rest of the testsuite since the outcome of a test is not the results that the test itself reports, but whether the result is the expected one. -- janis at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |janis at gcc dot gnu dot org |dot org | Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2005-12-12 17:57:54 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25352