public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
	       gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [debug-early] C++ clones and limbo DIEs
Date: Wed, 28 Jan 2015 19:47:00 -0000	[thread overview]
Message-ID: <54C92FA8.9040005@redhat.com> (raw)
In-Reply-To: <54C92A80.80306@redhat.com>

On 01/28/2015 01:29 PM, Aldy Hernandez wrote:
> +  /* It is rather unfortunate that Cilk creates trees this late
> +     (during gimplification).  However, until this gets fixed,
> +     specially handle emitting DWARF for this new function and
> +     immediately clean up the limbo_die_list where the new function's
> +     DIE will inevitably end up.  */

Why does it go on limbo_die_list at all?

> I noticed dwarf2out's gen_member_die() disallows generation of clones earlier, by design:
>
>      /* Don't include clones in the member list.  */
>      if (DECL_ABSTRACT_ORIGIN (member))
>        continue;
>
> I played around trying to disable this "feature", but my approach ran into various walls, and I decided instead to attack it from the front-end side. The attached patch generates early DIEs for the C++ clones in the C++ parser. I'd be (un)happy to revisit the dwarf2out approach if it's deemed more appropriate.

I'd still like to understand why disabling this doesn't work; I don't 
like the special handling of clones in the front end.

Jason

  reply	other threads:[~2015-01-28 18:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16  3:11 Aldy Hernandez
2015-01-16  4:30 ` Jason Merrill
2015-01-16 11:03   ` Richard Biener
2015-01-16 16:38     ` Jason Merrill
2015-01-16 18:09       ` Aldy Hernandez
2015-01-16 18:51       ` Richard Biener
2015-01-28 19:44     ` Aldy Hernandez
2015-01-16 17:54   ` Aldy Hernandez
2015-01-16 21:38     ` Jason Merrill
2015-01-23 19:53       ` Aldy Hernandez
2015-01-26  9:21         ` Richard Biener
2015-01-27 22:33         ` Jason Merrill
2015-01-28 19:24           ` Aldy Hernandez
2015-01-28 19:32             ` Aldy Hernandez
2015-01-28 19:47               ` Jason Merrill [this message]
2015-01-30 22:15                 ` Aldy Hernandez
2015-01-30 22:23                   ` Jason Merrill
2015-01-31  7:28                     ` Aldy Hernandez
2015-02-01  6:27                       ` Jason Merrill
2015-02-01  8:43                         ` Richard Biener
2015-02-02  3:15                         ` Aldy Hernandez
2015-02-02  4:16                           ` Jason Merrill
2015-02-05  0:27                             ` Aldy Hernandez
2015-02-05 20:11                               ` Jason Merrill
2015-02-06  1:15                                 ` Aldy Hernandez
2015-02-06 14:02                                   ` Jason Merrill
2015-02-06 16:42                                     ` Aldy Hernandez
2015-02-06 17:40                                       ` Jason Merrill
2015-02-06 17:47                                         ` Aldy Hernandez
2015-02-10 10:52                                       ` Richard Biener
2015-02-10 17:58                                         ` Jason Merrill
2015-02-12 18:04                                         ` Aldy Hernandez
2015-02-12 19:27                                           ` Jason Merrill
2015-02-16 20:46                                             ` Aldy Hernandez
2015-02-01  8:42                     ` Richard Biener
2015-02-02  1:48                       ` 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=54C92FA8.9040005@redhat.com \
    --to=jason@redhat.com \
    --cc=aldyh@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.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).