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: gdb-patches@sources.redhat.com, Elena Zannoni <ezannoni@redhat.com>
Subject: Re: [RFA/dwarf] Optimize partial DIE reading for uninteresting DIEs
Date: Fri, 27 Feb 2004 02:58:00 -0000	[thread overview]
Message-ID: <vt2wu69jkiv.fsf@zenia.home> (raw)
In-Reply-To: <20040226231255.GC8487@nevyn.them.org>


Daniel Jacobowitz <drow@false.org> writes:
> You're mistaken about the expense.  In particular read_unsigned_leb128
> is much slower than skip_uleb128 because of the computations to build
> the result; IIRC variable shifts are expensive.  Yes, this was measured
> with an optimized build and a non-intrusive profiler.  There's also the
> different memory access patterns.

No kidding.  I'm amazed.  Okay.

> Most of the speedup comes from not reading in the attribute values,
> though.

If what you say above is so, then two distinct versions of the
attribute traversal are clearly called for.

It would be interesting to compare profiling results between two GDB's
that differ only in whether they use your attribute skipper or the
attribute value reader.


  reply	other threads:[~2004-02-27  2:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25  3:06 Daniel Jacobowitz
2004-02-26 22:28 ` Jim Blandy
2004-02-26 23:12   ` Daniel Jacobowitz
2004-02-27  2:58     ` Jim Blandy [this message]
2004-02-27  3:03       ` Daniel Jacobowitz
2004-03-19  0:09         ` Daniel Jacobowitz
2004-03-09 19:58           ` Daniel Jacobowitz
2004-03-19  0:09           ` Jim Blandy
2004-03-10 14:56             ` 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=vt2wu69jkiv.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=drow@false.org \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.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