From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: per-inferior register cache for gdbserver
Date: Sat, 20 Apr 2002 18:23:00 -0000 [thread overview]
Message-ID: <3CC2147B.1040100@cygnus.com> (raw)
In-Reply-To: <20020420145943.A25321@nevyn.them.org>
> Um, would there be more benefit in getting this sort of thing
>> implemented in the core of GDB? I just don't see a per-lwp cache in the
>> remote target making much difference to GDB's thread debugging performance.
> I can get numbers later on how many register fetches it
> actually saves; I suspect it's fairly small.
Can you please add a comment to the code explaining this - it more of a
design benefit than a performance benefit (the performance gains are
unknown).
You'll notice that I'm sitting on the frame cache patch because I'm
still analyzing its effect. GDB already contains too much code that
``claims to improve performance''.
enjoy,
Andrew
next prev parent reply other threads:[~2002-04-21 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 10:22 Daniel Jacobowitz
2002-04-20 11:48 ` Andrew Cagney
2002-04-20 11:59 ` Daniel Jacobowitz
2002-04-20 18:23 ` Andrew Cagney [this message]
2002-06-13 12:29 ` Daniel Jacobowitz
2002-04-24 16:31 ` Michael Snyder
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=3CC2147B.1040100@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.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