public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
	Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, testsuite] Allow braces around relative line numbers
Date: Sat, 15 Apr 2017 15:54:00 -0000	[thread overview]
Message-ID: <9C950922-BD66-43A0-8B08-2F096C9ED728@comcast.net> (raw)
In-Reply-To: <6515ea22-c85d-8de1-3224-fb996e729cee@mentor.com>

On Apr 15, 2017, at 1:07 AM, Tom de Vries <Tom_deVries@mentor.com> wrote:
> I've attached two patches:
> 
> - second patch is the result of running the script.

> Second patch OK for stage4/stage1 trunk?

Ok.

> [ I'm not sure if the first patch is useful enough to commit to contrib. ]

Once the script it run, we shouldn't have to run it again.  So, I think it can live as a reference on the mailing list.

> 2017-04-14  Tom de Vries  <tom@codesourcery.com>
> 
> 	* g++.dg/parse/error11.C: Remove braces around line number in dejagnu
> 	  directive.
> 	* g++.dg/parse/error3.C: Same.
> 	* g++.old-deja/g++.pt/niklas01a.C: Same.
> 	* gcc.dg/990506-0.c: Same.
> 	* gcc.dg/cpp/19990413-1.c: Same.
> 	* gcc.dg/cpp/pragma-1.c: Same.
> 	* gcc.dg/cpp/pragma-2.c: Same.
> 	* gcc.dg/m-un-2.c: Same.
> 	* objc.dg/private-1.m: Same.

      reply	other threads:[~2017-04-15 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  7:45 Tom de Vries
2017-03-28 22:24 ` Jakub Jelinek
2017-04-15  8:34   ` Tom de Vries
2017-04-15 15:54     ` Mike Stump [this message]

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=9C950922-BD66-43A0-8B08-2F096C9ED728@comcast.net \
    --to=mikestump@comcast.net \
    --cc=Tom_deVries@mentor.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=ro@CeBiTec.Uni-Bielefeld.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).