From: Joern Rennecke <joern.rennecke@superh.com>
To: msnyder@redhat.com (Michael Snyder)
Cc: joern.rennecke@superh.com (Joern Rennecke),
amylaar@fairadsl.co.uk (Joern Rennecke),
gdb-patches@sources.redhat.com
Subject: Re: [RFA (revised)] sh-sim, expand the opcode table
Date: Thu, 12 Feb 2004 12:48:00 -0000 [thread overview]
Message-ID: <200402121248.i1CCm8o08759@linsvr1.uk.superh.com> (raw)
In-Reply-To: <402A81B9.6080009@redhat.com> from "Michael Snyder" at Feb 11, 2004 11:25:45
> Imprecisely speaking, they did not seem to make any difference at all.
> The number of new insns is actually not that great -- they only bring
> the switch statement up to about 290 cases.
OK. I think we can live with the 1% slowdown then, considering that
we expand the expressiveness of the jump table in a way that should be
good for several decades.
When I initailly added the sh-dsp stuff, the slowdown was much worse,
which is why I then spent some time optimizing the simulator till the
performance was better than it was before the sh-dsp support was added.
FWIW, we don't actually benefit much from technological progress here
to mitigate slowdowns, because we already have rising numbers of
multilibs, compiler options, and sheer volume of tests to go through,
which is why simulator performance is still more critical than gcc
build times for total regression test time.
next prev parent reply other threads:[~2004-02-12 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 0:40 Michael Snyder
2004-02-11 12:33 ` Joern Rennecke
2004-02-11 19:25 ` Michael Snyder
2004-02-12 12:48 ` Joern Rennecke [this message]
2004-02-12 19:32 ` 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=200402121248.i1CCm8o08759@linsvr1.uk.superh.com \
--to=joern.rennecke@superh.com \
--cc=amylaar@fairadsl.co.uk \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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