From: Paolo Carlini <paolo.carlini@oracle.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>
Subject: [C++ Patch PING] (was: [C++ Patch] PR 62315 ("do not print typename in diagnostic if the original code does not have it"))
Date: Fri, 23 Jun 2017 09:53:00 -0000 [thread overview]
Message-ID: <f6234cbf-7f6f-cd76-48ea-203a0bdf81ae@oracle.com> (raw)
In-Reply-To: <689cbd6e-7974-4aa9-9361-9f04f920d9a8@oracle.com>
Hi,
gently pingning this:
On 02/06/2017 10:35, Paolo Carlini wrote:
> Hi,
>
> a while ago Manuel noticed that printing 'typename' in error messages
> about missing 'typename' can be confusing. That seems easy to fix, in
> fact we already handle correctly a similar situation in
> grokdeclarator. Tested x86_64-linux.
https://gcc.gnu.org/ml/gcc-patches/2017-06/msg00099.html
Thanks!
Paolo.
next prev parent reply other threads:[~2017-06-23 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 8:35 [C++ Patch] PR 62315 ("do not print typename in diagnostic if the original code does not have it") Paolo Carlini
2017-06-23 9:53 ` Paolo Carlini [this message]
2017-06-23 20:40 ` Jason Merrill
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=f6234cbf-7f6f-cd76-48ea-203a0bdf81ae@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).