This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Excess errors in testcases (was Re: [RFC]g++.dg/parse/undefined1.C fails)
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Cc: "pcarlini at unitus dot it" <pcarlini at unitus dot it>
- Date: Sat, 25 Jan 2003 12:32:02 -0800
- Subject: Re: Excess errors in testcases (was Re: [RFC]g++.dg/parse/undefined1.C fails)
In fact that's not the only testcase I have with the same behavior:
With the old parser the testcase ICE'd. With the new parser we don't
have an ICE, but a couple of excess messages in the lines with follow
the errorneous ones. (I don't blame the parser for that - the code *is*
illegal. I don't even think that we have to fix such a behavior.)
And certainly that's not a regression; changing an ICE into even a bogus
error message is probably an improvement. (At least you can go on and
perhaps say something sensible about some later part of the code.)
Since we don't want ICEs to creep back in there should be a testcase
neverthess IMHO. The question, however, is: How can we make one?
I thought there was something like "dg-bogus" that you could use to say
that an error comes out here, but shouldn't; then you can XFAIL just that
line.
If there's not, I'd just add extra dg-error messages, with a comment.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com