public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [patch] Fix 100x slowdown regression on DWZ files
Date: Wed, 01 Oct 2014 23:57:00 -0000	[thread overview]
Message-ID: <CADPb22Q2r9Vnne5rDapAy=AuD2AKBU01TRANw3djo5Xk1icvNw@mail.gmail.com> (raw)
In-Reply-To: <21548.37770.274873.760290@ruffy2.mtv.corp.google.com>

On Wed, Oct 1, 2014 at 4:51 PM, Doug Evans <dje@google.com> wrote:
> [...]
> OTOH, I do want to avoid any confusion that this patch may inadvertently
> introduce. For example, IIUC with your patch as is,
> if we read a partial_unit first, before a compile_unit
> that has the same stmt_list value, we'll do more processing in
> dwarf_decode_lines than we really need to since we only need a file
> number to symtab mapping. And if we later read in a compile_unit
> with the same stmt_value we'll call dwarf_decode_lines again,
> and this time we need the pc/line mapping it computes.
> Whereas if we process these in the opposite order we'll only call
> dwarf_decode_lines once. I'm sure this will be confusing at first
> to some later developer going through this code.
> [I could be missing something of course, and I'm happy for any corrections.]

Ah, I guess the offset_in_dwz flag will ensure dwarf_decode_lines gets called
twice regardless of order.  But is that the only reason for the flag?

  reply	other threads:[~2014-10-01 23:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 19:44 Jan Kratochvil
2014-10-01 23:51 ` Doug Evans
2014-10-01 23:57   ` Doug Evans [this message]
2014-10-02 15:57   ` [patchv2] " Jan Kratochvil
2014-11-28 21:29     ` ping: " Jan Kratochvil
2014-12-31 19:23     ` ping^2: " Jan Kratochvil
2015-01-08  1:45       ` Doug Evans
2015-01-09  0:32         ` Doug Evans
2015-01-12 17:13           ` Jan Kratochvil
2015-01-12 17:26             ` Doug Evans
2015-01-14 20:26         ` [patchv3] " Jan Kratochvil
2015-01-22 18:46           ` Doug Evans
2015-01-22 18:57             ` Jan Kratochvil
2015-01-24 12:32               ` Doug Evans
2015-01-24 21:27                 ` [commit+7.9] " Jan Kratochvil
2015-01-25 16:17                   ` Jan Kratochvil

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='CADPb22Q2r9Vnne5rDapAy=AuD2AKBU01TRANw3djo5Xk1icvNw@mail.gmail.com' \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).