Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: DW_AT_specification: long ago GDB change
Date: Thu, 15 Apr 2004 05:20:00 -0000	[thread overview]
Message-ID: <vt2ad1d6crg.fsf@zenia.home> (raw)


Back in 1999, you posted this patch:

    http://sources.redhat.com/ml/gdb-patches/1999-q4/msg00325.html

Do you know why you tested for the presence of DW_AT_specification, as
well as DW_AT_declaration?

I can't think of a case where a die would be a declaration, but also
refer to a specification; since DW_AT_specification generally points
from definitions to previous declarations, I'd rather expect
specifications to point at declarations.  And even if a declaration
did have a specification, it would still be a declaration.

Looking at the only code in gcc/dwarf2out.c that adds
DW_AT_specification attributes to dies supports this:

    /* Add an AT_specification attribute to a DIE, and also make the back
       pointer from the specification to the definition.  */

    static inline void
    add_AT_specification (dw_die_ref die, dw_die_ref targ_die)
    {
      add_AT_die_ref (die, DW_AT_specification, targ_die);
      if (targ_die->die_definition)
        abort ();
      targ_die->die_definition = die;
    }

I guess if there were several declarations chained together,
eventually pointing to a definition, then the intermediate dies could
have both attributes.  Does this happen?


             reply	other threads:[~2004-04-15  5:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15  5:20 Jim Blandy [this message]
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

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=vt2ad1d6crg.fsf@zenia.home \
    --to=jimb@redhat.com \
    --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