Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: [rfc] Frame based register cache / frame->unwind
Date: Sun, 14 Apr 2002 18:48:00 -0000	[thread overview]
Message-ID: <20020414214916.A25012@nevyn.them.org> (raw)
In-Reply-To: <3CB9ED82.8050007@cygnus.com>

On Sun, Apr 14, 2002 at 04:58:42PM -0400, Andrew Cagney wrote:
> Hello,
> 
> To pull together several apparently random threads.  The attached is a 
> work in progress to add a frame based register cache to GDB.  It appears 
> to work - NetBSD/PPC shows no regressions.
> 
> Performance is hard to quantify(1) but looks positive.  Using a native 
> GDB (not typical for me :-) it appears that each frame is ~2% slower to 
> create (``(gdb) up'').  Once created, the frame is ~20-25% faster 
> (``(gdb) info registers'').

You might want to try timing the testsuite with and without this patch
(using /usr/bin/time et al., to get real/user/sys times) and see what
changes.  It'll probably be negligible, but you never know.

> I'm not too worried about the apparent 2% overhead per frame create 
> though.  With the patch applied, the code ends up maintaining both this 
> new cache and the old ->saved_regs table.  Rewriting a target to just 
> use the ->unwind_cache, should, I think, claw back the 2% and then some 
> - less need to go out to the target.

Completely agree.

> 
> There are two parts to the change and I'll describe each in turn.  The 
> final patch will likely be committed as two parts.

Looks wonderful to me!

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-04-15  1:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-14 13:58 Andrew Cagney
2002-04-14 18:48 ` Daniel Jacobowitz [this message]
2002-04-16  8:10   ` Andrew Cagney
2002-04-16  9:14 ` Kevin Buettner
2002-04-16 10:08   ` Andrew Cagney
2002-04-17 10:04     ` Andrew Cagney

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=20020414214916.A25012@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@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