From: Jason Merrill <jason@redhat.com>
To: IainS <developer@sandoe-acoustics.co.uk>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [Patch c++] (__attribute__((deprecated)), part a) Fix PR17729
Date: Wed, 09 Jun 2010 03:29:00 -0000 [thread overview]
Message-ID: <4C0F0855.3060005@redhat.com> (raw)
In-Reply-To: <F62C4460-7038-49D6-B361-48E199660D32@sandoe-acoustics.co.uk>
On 06/08/2010 07:13 PM, IainS wrote:
> the question then, is how to prevent the duplicates, since those places
> are called from more than one part of the process (or, at least, they
> were when I last looked).
For non-function members, I think removing the call in
finish_class_member_access_expr ought to do the trick, letting
build_class_member_access_expr handle the warning.
For functions, perhaps just warning in mark_used would work. Then
removing the calls in build_over_call and build_call_a and conditioning
the one in finish_id_expression on !is_overloaded_fn.
Jason
next prev parent reply other threads:[~2010-06-09 3:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 12:47 IainS
2010-06-08 23:12 ` Jason Merrill
2010-06-09 0:26 ` IainS
2010-06-09 3:29 ` Jason Merrill [this message]
2010-07-19 17:11 ` IainS
2010-07-19 17:59 ` Jason Merrill
2010-07-21 13:43 ` IainS
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=4C0F0855.3060005@redhat.com \
--to=jason@redhat.com \
--cc=developer@sandoe-acoustics.co.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).