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: [patchv3] Fix 100x slowdown regression on DWZ files
Date: Sat, 24 Jan 2015 12:32:00 -0000	[thread overview]
Message-ID: <CADPb22Q7jL456mQQ6JVEa6C-Ajv1OPjo=oWZ8-juHCjrkaF1eA@mail.gmail.com> (raw)
In-Reply-To: <20150122185509.GA16253@host2.jankratochvil.net>

On Thu, Jan 22, 2015 at 10:55 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Thu, 22 Jan 2015 19:45:08 +0100, Doug Evans wrote:
>> In my mind it's easier to just treat a non-NULL value for line_header_hash
>> as the flag to decide whether we're using the hash (instead of
>> seen_partial_unit).
>
> Yes, sure I agree.  I just haven't realized this simplificaton while coding it.
>
>
>> Sound ok?
>
> Yes, I am fine with your change; so I expect you can check it in when you ask
> this way.

Can you check it in?  Thanks.

  reply	other threads:[~2015-01-24  1:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 19:44 [patch] " Jan Kratochvil
2014-10-01 23:51 ` Doug Evans
2014-10-01 23:57   ` Doug Evans
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 [this message]
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='CADPb22Q7jL456mQQ6JVEa6C-Ajv1OPjo=oWZ8-juHCjrkaF1eA@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).