Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Jason Merrill <jason@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: DW_AT_specification: long ago GDB change
Date: Fri, 16 Apr 2004 21:29:00 -0000	[thread overview]
Message-ID: <vt2ekqnzkbb.fsf@zenia.home> (raw)
In-Reply-To: <20040416141520.GB9718@nevyn.them.org>


Daniel Jacobowitz <drow@false.org> writes:
> On Fri, Apr 16, 2004 at 08:49:16AM -0400, Jason Merrill wrote:
> > On 15 Apr 2004 17:19:17 -0500, Jim Blandy <jimb@redhat.com> wrote:
> > 
> > > Here are the attributes I see that we shouldn't search for in dies
> > > referenced by DW_AT_specification, but which are reasonable to look
> > > for in dies referred to by DW_AT_abstract_origin:
> > >
> > >   - DW_AT_declaration
> > >   - DW_AT_decl_column
> > >   - DW_AT_decl_file
> > >   - DW_AT_decl_line
> > 
> > I disagree about the other three; if the definition has different source
> > coordinates, it will have the attributes.  If it doesn't, there's no reason
> > to emit them again, and we should look them up in the declaration.
> 
> Yeah, that makes sense to me.  I'd forgotten about the peeking through 
> DW_AT_specification behavior for DW_AT_declaration; thanks for the kick 
> in the right direction.

Okay.  So then DW_AT_declaration is the only thing that needs to be
blocked.



      parent reply	other threads:[~2004-04-16 21:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15  5:20 Jim Blandy
2004-04-15 13:52 ` Jason Merrill
2004-04-15 22:22   ` Jim Blandy
2004-04-16 12:49     ` Jason Merrill
     [not found]       ` <20040416141520.GB9718@nevyn.them.org>
2004-04-16 21:29         ` Jim Blandy [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=vt2ekqnzkbb.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --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