From: Jason Merrill <jason@redhat.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [debug-early] Handle specification of class scoped static functions
Date: Fri, 03 Apr 2015 14:48:00 -0000 [thread overview]
Message-ID: <551EA84E.7080200@redhat.com> (raw)
In-Reply-To: <550CB740.6040305@redhat.com>
On 03/20/2015 08:11 PM, Aldy Hernandez wrote:
> + /* For class scoped static functions, the dumped early
> + version was the declaration, whereas the next time
> + around with a different context should be the
> + specification. In this case, avoid reusing the DIE, but
> + generate a specification below. E.g.:
> +
> + class C {
> + public:
> + static void moo () {}
> + }; */
> + || !is_cu_die (context_die))
Why do we still need this added (relative to trunk)? Are we getting
here multiple times with class context_die?
Also, the comment seems redundant with the comment immediately above.
Jason
next prev parent reply other threads:[~2015-04-03 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 17:56 Aldy Hernandez
2015-03-20 21:21 ` Jason Merrill
2015-03-21 0:11 ` Aldy Hernandez
2015-04-03 14:48 ` Jason Merrill [this message]
2015-04-13 18:01 ` Aldy Hernandez
2015-04-13 21:05 ` Jason Merrill
2015-04-13 21:08 ` 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=551EA84E.7080200@redhat.com \
--to=jason@redhat.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
/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).