Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: gdb-patches@sources.redhat.com
Cc: Jim Blandy <jimb@redhat.com>, Elena Zannoni <ezannoni@redhat.com>
Subject: Re: [RFA/dwarf] Don't process types multiple times
Date: Wed, 25 Feb 2004 17:02:00 -0000	[thread overview]
Message-ID: <yf2fzczqehw.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20040225044206.GA23242@nevyn.them.org> (Daniel Jacobowitz's message of "Tue, 24 Feb 2004 23:42:06 -0500")

On Tue, 24 Feb 2004 23:42:06 -0500, Daniel Jacobowitz <drow@false.org> said:

> There are two ways that we can process a general DIE: process_die or
> read_type_die.  Children of particular DIE types may be processed
> directly, but these are the only major dispatch points.  It's
> interesting to notice that almost everything called from
> read_type_die starts with "if (die->type) return": everything but
> enumeration types and aggregate types, in fact.  This means that if
> the first reference to an enumeration or aggregate type is a
> DW_AT_type or DW_AT_containing_type in a DIE numerically before the
> type's DIE, we'll end up calling new_symbol for it twice.

Yeah, that had been bothering me for a while, too.

In the FIXME comment, could you add your name and the date?

David Carlton
carlton@kealia.com


  reply	other threads:[~2004-02-25 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25  4:42 Daniel Jacobowitz
2004-02-25 17:02 ` David Carlton [this message]
2004-03-05  2:55 ` Daniel Jacobowitz
2004-03-19  0:09   ` Daniel Jacobowitz
2004-03-12 23:45 ` Jim Blandy
2004-03-15 22:08   ` Andrew Cagney
2004-03-19  0:09     ` Andrew Cagney
2004-03-19  0:09   ` Jim Blandy
2004-03-19  0:09   ` Daniel Jacobowitz
2004-03-14 21:10     ` Daniel Jacobowitz

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=yf2fzczqehw.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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