From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: PATCH: per-inferior register cache for gdbserver
Date: Thu, 13 Jun 2002 12:29:00 -0000 [thread overview]
Message-ID: <20020613193000.GA6124@nevyn.them.org> (raw)
In-Reply-To: <3CC2147B.1040100@cygnus.com>
On Sat, Apr 20, 2002 at 09:23:07PM -0400, Andrew Cagney wrote:
> >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).
Good idea, done.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
2002-06-13 Daniel Jacobowitz <drow@mvista.com>
* gdbserver/regcache.c: Add comment.
Index: regcache.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/regcache.c,v
retrieving revision 1.5
diff -u -p -r1.5 regcache.c
--- regcache.c 11 Jun 2002 17:32:39 -0000 1.5
+++ regcache.c 13 Jun 2002 19:28:07 -0000
@@ -25,6 +25,10 @@
#include <stdlib.h>
#include <string.h>
+/* The private data for the register cache. Note that we have one
+ per inferior; this is primarily for simplicity, as the performance
+ benefit is minimal. */
+
struct inferior_regcache_data
{
int registers_valid;
next prev parent reply other threads:[~2002-06-13 19:29 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
2002-06-13 12:29 ` Daniel Jacobowitz [this message]
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=20020613193000.GA6124@nevyn.them.org \
--to=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