This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/25352] xfail within dg-do command has no effect
- From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Dec 2005 18:36:29 -0000
- Subject: [Bug testsuite/25352] xfail within dg-do command has no effect
- References: <bug-25352-578@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla 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 fix should go there. However I
don't feel strongly about whether to fix it in GCC additionally and separately.
If forced to pick, I'd lean towards dejagnu only since I'll upgrade once the
new version is out.
If we don't fix it in GCC, then we should remove the documentation that says it
works. Perhaps we could recommend dg-xfail-if instead?
Either way we should probably continue to remove the existing dg-do xfails
since we'll start getting a bunch of spurious XPASSes once people start
upgrading to the new dejagnu. I'll try and handle the ones that trigger on my
platforms but some I can't test to know whether simply to remove the xfail or
change it to dg-xfail-if.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25352