From: "Joseph S. Myers" <jsm@polyomino.org.uk>
To: Adam Nemet <anemet@lnxw.com>
Cc: Andreas Schwab <schwab@suse.de>,
Richard Henderson <rth@redhat.com>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: PR middle-end/18160
Date: Wed, 27 Oct 2004 09:52:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0410270947300.22311@digraph.polyomino.org.uk> (raw)
In-Reply-To: <16767.17669.263621.205498@anemet1.lynx.com>
On Tue, 26 Oct 2004, Adam Nemet wrote:
> * gcc.dg/pr18160.c: New test.
> * gcc.dg/pr18160-1.c: New test.
You should use pr18160-1.c, pr18160-2.c unless there's some specific
reason not to do so. When adding just a single testcase for a problem, it
should normally include the -1 suffix - in case future related tests
arise.
> + g(&x); /* { dg-error "address of register variable" } */
dg-error does not test that something is a hard error, for now you need to
include the "error: " prefix in the tested message explicitly.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
joseph@codesourcery.com (CodeSourcery mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)
next prev parent reply other threads:[~2004-10-27 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16766.43717.959860.195034@anemet1.lynx.com>
[not found] ` <20041026195203.GA15086@redhat.com>
[not found] ` <16766.46685.198957.191723@anemet1.lynx.com>
[not found] ` <20041026202657.GA15269@redhat.com>
[not found] ` <16766.54682.82730.11990@anemet1.lynx.com>
[not found] ` <20041026224419.GA15592@redhat.com>
[not found] ` <16766.57917.483995.480374@anemet1.lynx.com>
[not found] ` <jehdohgh9z.fsf@sykes.suse.de>
2004-10-27 8:26 ` Adam Nemet
2004-10-27 9:52 ` Joseph S. Myers [this message]
2004-10-27 9:57 ` Eric Botcazou
2004-10-27 22:57 ` Adam Nemet
2004-10-27 23:00 ` Richard Henderson
2004-10-27 16:53 ` Richard Henderson
2004-10-27 17:35 ` 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=Pine.LNX.4.61.0410270947300.22311@digraph.polyomino.org.uk \
--to=jsm@polyomino.org.uk \
--cc=anemet@lnxw.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
--cc=schwab@suse.de \
/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).