public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/20771] Duplicate PCH test names Date: Wed, 21 May 2008 00:07:00 -0000 [thread overview] Message-ID: <20080521000608.17419.qmail@sourceware.org> (raw) In-Reply-To: <bug-20771-230@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from janis at gcc dot gnu dot org 2008-05-21 00:05 ------- Subject: Bug 20771 Author: janis Date: Wed May 21 00:04:45 2008 New Revision: 135696 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=135696 Log: PR testsuite/20771 * lib/dg-pch.exp: Move a flag in arguments to dg-test to differentiate compile results for pch test lines in gcc.sum. * gcc.dg/pch/counter-2.c: Add comments to dg-error directives to make them unique in gcc.sum. * gcc.dg/pch/valid-1.c: Ditto. * gcc.dg/pch/valid-2.c: Ditto. * gcc.dg/pch/valid-3.c: Ditto. * gcc.dg/pch/warn-1.c: Same for dg-warning. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/pch/counter-2.c trunk/gcc/testsuite/gcc.dg/pch/valid-1.c trunk/gcc/testsuite/gcc.dg/pch/valid-2.c trunk/gcc/testsuite/gcc.dg/pch/valid-3.c trunk/gcc/testsuite/gcc.dg/pch/warn-1.c trunk/gcc/testsuite/lib/dg-pch.exp -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20771
next prev parent reply other threads:[~2008-05-21 0:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20771-230@http.gcc.gnu.org/bugzilla/> 2008-05-14 0:00 ` janis at gcc dot gnu dot org 2008-05-14 0:29 ` joseph at codesourcery dot com 2008-05-21 0:07 ` janis at gcc dot gnu dot org [this message] [not found] <bug-20771-4@http.gcc.gnu.org/bugzilla/> 2012-06-13 22:56 ` janis at gcc dot gnu.org 2012-06-13 23:03 ` janis at gcc dot gnu.org 2012-07-09 22:11 ` janis at gcc dot gnu.org 2005-04-05 19:10 [Bug testsuite/20771] New: " jsm28 at gcc dot gnu dot org 2005-04-05 23:33 ` [Bug testsuite/20771] " pinskia 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=20080521000608.17419.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).