public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/30612] Testsuite cannot detect duplicated error/warning messages Date: Sat, 17 Apr 2010 12:19:00 -0000 [thread overview] Message-ID: <20100417121908.26477.qmail@sourceware.org> (raw) In-Reply-To: <bug-30612-13511@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from iains at gcc dot gnu dot org 2010-04-17 12:19 ------- It seems that /* { dg-warning "xxxx" "" } */ Is eating all lines where xxxx occurs together with the line on which the warning is declared. Otherwise, we'd get an excess errors (which would be perfectly fine as a way of detecting this). you can't even do this: line-with-dup-warning // { dg-warning "match-text" "" } // { dg-warning "match-text" "" { target *-*-* } last-line-no } -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30612
next prev parent reply other threads:[~2010-04-17 12:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-27 16:56 [Bug testsuite/30612] New: " manu at gcc dot gnu dot org 2010-04-17 12:19 ` iains at gcc dot gnu dot org [this message] 2010-04-17 12:56 ` [Bug testsuite/30612] " manu at gcc dot gnu dot org 2010-04-19 16:19 ` iains at gcc dot gnu dot org 2010-04-19 17:42 ` lopezibanez at gmail dot com 2010-04-19 18:26 ` iains at gcc dot gnu dot org
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=20100417121908.26477.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).