From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc@gcc.gnu.org
Subject: How to test for duplicate error messages
Date: Mon, 29 Nov 2004 14:24:00 -0000 [thread overview]
Message-ID: <200411291414.iATEEPBN029704@relay.rwth-aachen.de> (raw)
Hi,
I've got some questions regarding duplicate error messages in the testsuite:
How do I test that an error mesage isn't emitted twice
(like in g++.dg/parse/dtor2.C )?
I could only find g++.dg/other/error8.C which isn't working as expected
IMHO. The last three lines read
// The duplicated error messages are xfailed for now (tracked in the PR)
// { dg-bogus "" "duplicate error messages" { target *-*-* } 8 }
// { dg-bogus "" "duplicate error messages" { target *-*-* } 9 }
But
* the tests do PASS (it's not an XPASS!)
* the PR was closed
* trying to copy such a line to g++.dg/parse/dtor2.C didn't work
(I got PASS although there's a duplicate message).
So the questions are:
* How to check for duplicate error messages?
* How to fix g++.dg/other/error8.C ?
Regards,
Volker
next reply other threads:[~2004-11-29 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 14:24 Volker Reichelt [this message]
2004-11-30 2:58 ` Giovanni Bajo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200411291414.iATEEPBN029704@relay.rwth-aachen.de \
--to=reichelt@igpm.rwth-aachen.de \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).