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>
Cc: Jason Merrill <jason@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [debug-early] fix problem with template parameter packs
Date: Wed, 03 Jun 2015 13:18:00 -0000	[thread overview]
Message-ID: <CAFiYyc0ED7vRnfK+fC8u4wo0XJWfYznYe3Dhgp4Qw1U5U73ULw@mail.gmail.com> (raw)
In-Reply-To: <556EFB62.3040209@redhat.com>

On Wed, Jun 3, 2015 at 3:04 PM, Aldy Hernandez <aldyh@redhat.com> wrote:
> On 05/27/2015 03:34 PM, Jason Merrill wrote:
>
>> It occurs to me that the early-dwarf work should make
>> debug_abstract_function and most of the DECL_ABSTRACT handling obsolete.
>>   All we need to do is set DW_AT_inline during early debug and update it
>> during late debug if the function is inlined.
>
>
> This is certainly a cool idea.  I played around with this, and I think we
> should be able to get it to work.  However, this won't work for the LTO
> case, because dwarf2out currently works just as our pre-debug-early world
> did.  We don't have an early DIE we can annotate later.  At least, until we
> get Richi's DIE streaming idea working.
>
> We could temporarily make the LTO case behave like early-debug by emitting
> early DIEs after LTO stream in-- while we get DIE streaming implemented, or
> we could leave the DECL_ABSTRACT redesign post-richi-streaming.  I'm leaning
> towards the latter.

Yeah, I think we can delay this until I get the LTO bits working and merged
(well, I mostly have to sit down and re-do the tooling :/)

Richard.

> Thoughts?
>

  reply	other threads:[~2015-06-03 13:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05  2:29 Aldy Hernandez
2015-05-05 21:08 ` Jason Merrill
2015-05-05 21:33   ` Aldy Hernandez
2015-05-06 16:28     ` Jason Merrill
2015-05-26 17:02       ` Aldy Hernandez
2015-05-27 20:09         ` Jason Merrill
2015-05-28  8:19           ` Richard Biener
2015-06-03 13:05           ` Aldy Hernandez
2015-06-03 13:18             ` Richard Biener [this message]
2015-06-03 14:55               ` Aldy Hernandez
2015-06-04 18:39                 ` Jason Merrill
2015-06-04 18:57                   ` Jason Merrill
2015-06-05  1:53                     ` Aldy Hernandez
2015-06-05 11:02                       ` Aldy Hernandez
2015-06-05 14:02                       ` Jason Merrill
2015-06-05 15:24                         ` Aldy Hernandez
2015-06-05 16:32                           ` Jason Merrill
2015-06-05 16:54                             ` Aldy Hernandez
2015-06-05 17:05                               ` Jason Merrill
2015-06-04 22:21                 ` Jason Merrill
2015-06-05  5:00                   ` Aldy Hernandez

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=CAFiYyc0ED7vRnfK+fC8u4wo0XJWfYznYe3Dhgp4Qw1U5U73ULw@mail.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).