public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Aldy Hernandez <aldyh@redhat.com>,Jason Merrill
	<jason@redhat.com>,GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: LTO early debug, day 2
Date: Tue, 14 Apr 2015 17:02:00 -0000	[thread overview]
Message-ID: <3ED99F76-5E91-4D9A-A2D2-42A1E4572696@gmail.com> (raw)
In-Reply-To: <552D3FE2.8050900@redhat.com>

On April 14, 2015 6:27:14 PM GMT+02:00, Aldy Hernandez <aldyh@redhat.com> wrote:
>On 04/14/2015 06:35 AM, Richard Biener wrote:
>
>Richard, thank you so much for working on this.  It's good to see your 
>progress here.
>
>> the late dwarf generation is a bit awkward because it insists on
>creating
>> type DIEs for all sort of contexts when we process scope vars.  The
>type
>
>Types should be reused, are they not being reused from early to late
>dwarf?

They are not there in the late phase because they should not be needed
(They are inherited from early debug
But not explicitly rematerialized).

In fact the whole plan is to eventually
Not even have the 'tree' side of the types
Anymore.

Richard.

>
>> DIEs already exist, but only in early debug info.  I suspect we need
>to do
>> quite some dwarf2out refactoring to split early from late debug
>generation
>> in areas like that.  For the C++ example above we get some stray
>unused
>> type DIEs still.
>
>A pass to remove unused DIEs is on my TODO list.
>
>Aldy


      reply	other threads:[~2015-04-14 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 13:35 Richard Biener
2015-04-14 16:27 ` Aldy Hernandez
2015-04-14 17:02   ` Richard Biener [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=3ED99F76-5E91-4D9A-A2D2-42A1E4572696@gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=aldyh@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.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).