From: Nathan Sidwell <nathan@acm.org>
To: Volker Reichelt <v.reichelt@netcologne.de>, gcc@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>
Subject: Re: Errors in pairs
Date: Mon, 26 Mar 2018 11:17:00 -0000 [thread overview]
Message-ID: <ffe809b2-004d-72d7-9e8d-9f15c8ed2c8a@acm.org> (raw)
In-Reply-To: <e389e3ae-b576-eadd-5f3a-435df1c04841@netcologne.de>
On 03/24/2018 04:06 PM, Volker Reichelt wrote:
> Hi everybody,
>
> while bug-hunting I noticed that we emit lots of erros in pairs in
> check_final_overrider (cp/search.c), e.g.:
>
> Â error ("invalid covariant return type for %q+#D", overrider);
> Â error ("Â overriding %q+#D", basefn);
>
> I would expect the second line to be emitted as a note (using inform).
> Is there a reason for this or should that be changed?
Probably a sign the code predates 'inform' and/or the error-limit
option. As Paolo says, this should be changed.
nathan
--
Nathan Sidwell
prev parent reply other threads:[~2018-03-26 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 20:07 Volker Reichelt
2018-03-24 21:35 ` Paolo Carlini
2018-03-25 14:20 ` Volker Reichelt
2018-03-26 11:17 ` Nathan Sidwell [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=ffe809b2-004d-72d7-9e8d-9f15c8ed2c8a@acm.org \
--to=nathan@acm.org \
--cc=dmalcolm@redhat.com \
--cc=gcc@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).