[Bug testsuite/25352] xfail within dg-do command has no effect

2008-05-13 Thread janis at gcc dot gnu dot org
--- Comment #11 from janis at gcc dot gnu dot org 2008-05-13 22:19 --- Fixed, via documentation and workarounds. -- janis at gcc dot gnu dot org changed: What|Removed |Added --

[Bug testsuite/25352] xfail within dg-do command has no effect

2007-11-01 Thread janis at gcc dot gnu dot org
--- Comment #10 from janis at gcc dot gnu dot org 2007-11-01 16:22 --- Subject: Bug 25352 Author: janis Date: Thu Nov 1 16:22:36 2007 New Revision: 129823 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=129823 Log: gcc/ PR testsuite/25352 * doc/sourcebuild.texi (

[Bug testsuite/25352] xfail within dg-do command has no effect

2007-05-15 Thread ghazi at gcc dot gnu dot org
--- Comment #9 from ghazi at gcc dot gnu dot org 2007-05-15 17:47 --- (In reply to comment #8) > My recommendations are to document, in the description of test directives in > the GCC Internals manual, that xfail for dg-do is only honored for dg-do run > and ignored for other keywords, r

[Bug testsuite/25352] xfail within dg-do command has no effect

2007-05-10 Thread janis at gcc dot gnu dot org
--- Comment #8 from janis at gcc dot gnu dot org 2007-05-11 00:51 --- I had forgotten all about this. Today I checked to see how older versions of DejaGnu and GCC tests handled xfail for dg-do keywords other than "run". I only went back as far as GCC 3.0.4 and DejaGnu 1.4, but they als

[Bug testsuite/25352] xfail within dg-do command has no effect

2007-05-10 Thread ghazi at gcc dot gnu dot org
--- Comment #7 from ghazi at gcc dot gnu dot org 2007-05-10 17:44 --- Ben, Janis, Would you please offer an update on the status of this PR? I'm running into another situation where I need to xfail a dg-do link, and due to the issues discussed in this PR it doesn't work. Has dejagnu c

[Bug testsuite/25352] xfail within dg-do command has no effect

2005-12-14 Thread ghazi at gcc dot gnu dot org
--- Comment #6 from ghazi at gcc dot gnu dot org 2005-12-14 18:36 --- (In reply to comment #5) > Having GCC depend on a fix in > DejaGnu would not be popular unless there were other compelling reasons to > require people to upgrade. Thoughts? If the breakage is in dejagnu, certainly a

[Bug testsuite/25352] xfail within dg-do command has no effect

2005-12-14 Thread janis at gcc dot gnu dot org
--- Comment #5 from janis at gcc dot gnu dot org 2005-12-14 18:17 --- I've got an ugly fix that reaches up a couple of levels to get the variable from the DejaGnu proc that records that the test should be xfailed. Ben Elliston, who is a DejaGnu maintainer, says that 1.4.5 will be releas

[Bug testsuite/25352] xfail within dg-do command has no effect

2005-12-13 Thread janis at gcc dot gnu dot org
--- 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 dej

[Bug testsuite/25352] xfail within dg-do command has no effect

2005-12-12 Thread janis at gcc dot gnu dot org
--- Comment #3 from janis at gcc dot gnu dot org 2005-12-12 22:14 --- How embarrassing, I tried these things by adding new tests to gcc.test-framework and the awk script that checks the results was ignoring some of the results because of magic needed for the generated tests. Now I'm abl

[Bug testsuite/25352] xfail within dg-do command has no effect

2005-12-12 Thread janis at gcc dot gnu dot org
--- 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 direct

[Bug testsuite/25352] xfail within dg-do command has no effect

2005-12-11 Thread ghazi at gcc dot gnu dot org
--- Comment #1 from ghazi at gcc dot gnu dot org 2005-12-11 15:14 --- We probably should have some sort of dg conformance test directory with simple tests ensuring all the directives work as advertised. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25352