From: David Malcolm <dmalcolm@redhat.com>
To: Volker Reichelt <v.reichelt@netcologne.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] C++ parser: Fix typos in error messages
Date: Mon, 05 Jun 2017 15:33:00 -0000 [thread overview]
Message-ID: <1496676807.7551.95.camel@redhat.com> (raw)
In-Reply-To: <tkrat.a89cd200c3464511@netcologne.de>
On Tue, 2017-05-02 at 08:05 +0200, Volker Reichelt wrote:
> Hi,
>
> the following patch fixes two typos in error messages of the C++
> parser
> (which have gone unnoticed since GCC 3.4.0).
>
> Bootstrapped and regtested on x86_64-pc-linux-gnu.
> OK for trunk?
> Should this go also to GCC 7.2?
>
> Regards,
> Volker
>
>
> 2017-05-01 Volker Reichelt <v.reichelt@netcologne.de>
>
> * parser.c (cp_parser_base_specifier): Fix typos in error
> messages.
>
> Index: gcc/cp/parser.c
> ===================================================================
> --- gcc/cp/parser.c (revision 247445)
> +++ gcc/cp/parser.c (working copy)
> @@ -23716,7 +23716,7 @@
> if (virtual_p && !duplicate_virtual_error_issued_p)
> {
> cp_parser_error (parser,
> - "%<virtual%> specified more than once
> in base-specified");
> + "%<virtual%> specified more than once
> in base-specifier");
> duplicate_virtual_error_issued_p = true;
> }
>
> @@ -23736,7 +23736,7 @@
> && !duplicate_access_error_issued_p)
> {
> cp_parser_error (parser,
> - "more than one access specifier in
> base-specified");
> + "more than one access specifier in
> base-specifier");
> duplicate_access_error_issued_p = true;
> }
>
> ===================================================================
OK for both (with my "diagnostic messages" maintainer hat on).
Dave
prev parent reply other threads:[~2017-06-05 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 6:11 Volker Reichelt
2017-05-02 7:16 ` Volker Reichelt
2017-06-05 15:33 ` David Malcolm [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=1496676807.7551.95.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=v.reichelt@netcologne.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).