From: Jason Merrill <jason@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch] Replace a few more error + error with error + inform
Date: Thu, 29 Jun 2017 21:46:00 -0000 [thread overview]
Message-ID: <CADzB+2nqCjKr7i=fYkUoYaJGc_oUzH7rWszzsrLiMc2Uud6E1Q@mail.gmail.com> (raw)
In-Reply-To: <8407427e-d71a-e7ab-80b4-c43241044918@oracle.com>
OK.
On Fri, May 19, 2017 at 12:13 PM, Paolo Carlini
<paolo.carlini@oracle.com> wrote:
> Hi,
>
> while looking into some bugs (eg, c++/71464) I noticed a few more of those
> consecutive errors, which I propose to adjust per the below patchlet. The
> second case in add_method is a bit tricky because in principle we'd really
> like to be more specific (eg, clang talks about constructors which cannot be
> redeclared, member functions which cannot be redeclared and many more) and
> avoid verbose diagnostic, but in the below I only try to avoid emitting
> error + error... Tested x86_64-linux.
>
> Thanks, Paolo.
>
> /////////////////////
>
>
prev parent reply other threads:[~2017-06-29 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 16:15 Paolo Carlini
2017-06-29 8:56 ` Paolo Carlini
2017-06-29 21:46 ` Jason Merrill [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='CADzB+2nqCjKr7i=fYkUoYaJGc_oUzH7rWszzsrLiMc2Uud6E1Q@mail.gmail.com' \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paolo.carlini@oracle.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).