Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joern Rennecke <joern.rennecke@superh.com>
To: msnyder@redhat.com (Michael Snyder)
Cc: amylaar@fairadsl.co.uk (Joern Rennecke),
	joern.rennecke@superh.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] sh-sim: thislock/prevlock tweak
Date: Fri, 06 Feb 2004 12:39:00 -0000	[thread overview]
Message-ID: <200402061238.i16CcWl25143@linsvr1.uk.superh.com> (raw)
In-Reply-To: <4022D60A.5020905@redhat.com> from "Michael Snyder" at Feb 05, 2004 03:47:22

> Joern,
> 
> I don't fully understand this code, but it looks to me as if this
> minor change is needed.  Most other instructions appear to call
> the macro "L()" for the register that was explicitly the target
> of the instruction.

Looks sensible as far as I can see it; it would be helpful to have
enough context to see the full insn.
Note that L is part of the mechanism that approximates SH[123]
timing; SH4 timing is entirely different.  This makes a number of
the MA calls rather bizarre, where we simulate the timings of a
processor that doesn't implement the instructions in the first place.

In October I made a patch to implement SH4 timings (controlled by
an #ifdef SH4_TIMINGS), but it ended up a few percent slower than
the simulator before, so I thought we should really use a simulator
built with ACE_FAST for the c-torture simulator tests - even better if we can
make it processor specific, i.e. no DSP insns for non-dsp processors
and no FPU insns for non-fpu processors.  The mere presence of the
code seems to skew the memory layout and/or register allocation of the
'hot' code to make the simulator slower.  So that would require to
build separate binaries and a wrapper that invokes the right one,
or make dejagnu pick up a specifically tuned variant.
Then we had a lot of changes to the simulator for other functionality,
and I didn't have the time to make this into a current patch.
I'll forward a copy of my letter with the patch in case you or someone
else on the list want to pick it up.


  reply	other threads:[~2004-02-06 12:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19  4:14 [RFA] sh-sim: restructure expand_opcode Michael Snyder
2003-12-20 12:52 ` Joern Rennecke
2003-12-23  1:23   ` Michael Snyder
2003-12-31 16:09     ` Joern Rennecke
2004-01-06  1:06       ` Michael Snyder
2004-02-06  1:09   ` [RFA] sh-sim: thislock/prevlock tweak Michael Snyder
2004-02-06 12:39     ` Joern Rennecke [this message]
2004-02-06 19:35       ` Michael Snyder
2004-02-12 19:56         ` Michael Snyder
2004-02-12 21:23           ` Joern Rennecke

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=200402061238.i16CcWl25143@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