public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Jason Merrill <jason@redhat.com>,
	Aldy Hernandez <aldyh@redhat.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix early debug regression with DW_AT_string_length (PR debug/71906)
Date: Thu, 11 Aug 2016 12:36:00 -0000	[thread overview]
Message-ID: <20160811123606.GQ14857@tucnak.redhat.com> (raw)
In-Reply-To: <CAFiYyc3Lcdwezk28Mh7ovzJjA=R=tOAvrWPZXZ=H-9WTZ-38yw@mail.gmail.com>

Hi!

On Wed, Aug 10, 2016 at 12:23:06PM +0200, Richard Biener wrote:
> > Introducing another attribute that does the same thing as existing attribute
> > would be way too ugly.  In theory the reference class could be added to
> > DW_AT_string_length, I can ask on DWARF workgroup (but it might be too late
> > for DWARF 5), but that still doesn't solve the issue of the indirect params.
> >
> > How do you want to handle the debug info without ammending the early-generated
> > DWARF though?  Just by using it as abstract origins of everything and
> > ammending in copies?
> 
> Yes.

I've filed an enhancement request and got one positive feedback, but it is
going to be multiple months at best.
So, at least for non-LTO I'd strongly prefer to go with what the current
patch does, and for LTO we'd then have to ask GDB to implement the reference
class for DW_AT_string_length and then just use that instead, depending on
flag_lto or similar, or perhaps for dwarf4 and earlier don't emit for LTO
variable string length and keep it only for dwarf5+ (if the change is
approved).  For the indirect parms and LTO, I guess we'd need to create some
artificial VAR_DECL at function scope with DECL_VALUE_EXPR of *parm,
DECL_ARTIFICIAL, DECL_NAMELESS and reference that instead of the parm
itself.
With this, do you object to the current patch?

	Jakub

  reply	other threads:[~2016-08-11 12:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 16:53 Jakub Jelinek
2016-07-22 11:55 ` Richard Biener
2016-07-22 12:08   ` Jakub Jelinek
2016-07-22 12:39     ` Richard Biener
2016-08-01 10:44       ` Richard Biener
2016-08-09 14:36         ` Jakub Jelinek
2016-08-09 17:10           ` Richard Biener
2016-08-10  8:17             ` Jakub Jelinek
2016-08-10 10:23               ` Richard Biener
2016-08-11 12:36                 ` Jakub Jelinek [this message]
2016-08-11 14:09                   ` Richard Biener
2016-08-12 17:47 ` Jason Merrill
2016-08-12 17:57   ` Jakub Jelinek
2016-08-15 10:07     ` Jakub Jelinek

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=20160811123606.GQ14857@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=aldyh@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --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).