From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Performance optimize large bp_location count
Date: Wed, 14 Oct 2009 22:57:00 -0000 [thread overview]
Message-ID: <m34oq17fep.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091013223510.GA29950@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Wed, 14 Oct 2009 00:35:11 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> Still just this way it was a minimal changeset to get the same user
Jan> experience as the best breakpoints-modifying patch could be. After
Jan> other parts of GDB (symbol lookups) get accelerated more work may
Jan> be useful on this part.
This sounds reasonable to me.
Tom> I puzzled over the choice of a sorted array here, wondering if there
Tom> were perhaps some better data structure. A bit of rationale and
Tom> overview in the patch email would go a long way.
Jan> I do not remember it all but probably I just did not consider the
Jan> possibility of an incremental update, I tried the most easy patch
Jan> and it worked. Different data structure would be more appropriate
Jan> for the incremental update.
Thanks for this and your explanations, they were very useful.
Tom> It isn't obvious to me why this finds the leftmost element when there
Tom> are multiple overlapping ones. What am I missing?
Jan> Maybe another comment? (put there one before "if (b->...)")
Thanks.
Jan> 2009-10-14 Jan Kratochvil <jan.kratochvil@redhat.com>
Jan> Performance optimize large bp_location count.
Jan> * breakpoint.c (ALL_BP_LOCATIONS_SAFE): Remove.
[...]
Ok.
Tom
next prev parent reply other threads:[~2009-10-14 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 20:17 Jan Kratochvil
2009-10-13 18:34 ` Tom Tromey
2009-10-13 22:35 ` Jan Kratochvil
2009-10-14 22:57 ` Tom Tromey [this message]
2009-10-25 19:41 ` 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=m34oq17fep.fsf@fleche.redhat.com \
--to=tromey@redhat.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