Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: DJ Delorie <dj@redhat.com>
Subject: Re: [rx sim] add decode cache
Date: Thu, 29 Jul 2010 19:23:00 -0000	[thread overview]
Message-ID: <201007291523.07679.vapier@gentoo.org> (raw)
In-Reply-To: <201007291841.o6TIfcgn017022@greed.delorie.com>

[-- Attachment #1: Type: Text/Plain, Size: 1075 bytes --]

On Thursday, July 29, 2010 14:41:38 DJ Delorie wrote:
> This patch is a performance improvement for the RX simulator.  It
> stores the opcode decode information from libopcodes so that any given
> opcode need not be decoded more than once.  This, and some
> optimizations in the previous patch, results in the simulator taking
> about 60% of the time it used to take to run a given program.  On a
> 3.2GHz desktop, I get an effective 12.5MHz simulated time with full
> cycle stats, 14.5MHz with just cycle tracking, and 16MHz without cycle
> tracking.

if the rx sim is ultimately built on top of opc2c, and you're caching the 
results of that, then shouldnt it be possible to keep the cache in a generic 
place where everyone using opc2c would be able to leverage it ?

also, on a semi-related note, i cant find any documentation or info in the 
archives on opc2c.  it seems to have been quietly merged with the rx port and 
not really given any public info.  looking at the rx opc file, it seems like 
it'd be useful to port some peeps over to it.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-07-29 19:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29 18:42 DJ Delorie
2010-07-29 19:23 ` Mike Frysinger [this message]
2010-07-29 19:34   ` DJ Delorie
2010-07-29 21:42     ` Mike Frysinger
2010-07-29 22:00       ` DJ Delorie
2010-07-30  0:09         ` Mike Frysinger
2010-07-30  0:17           ` DJ Delorie
2010-07-30  1:04         ` Kevin Buettner

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=201007291523.07679.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=dj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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