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 loose ends
Date: Thu, 12 Feb 2004 22:39:00 -0000	[thread overview]
Message-ID: <200402122239.i1CMdJK12072@linsvr1.uk.superh.com> (raw)
In-Reply-To: <402BF664.1060508@redhat.com> from "Michael Snyder" at Feb 12, 2004 01:55:48

> 	* gencode.c (movt): Modifies R[n]; call 'L' macro.

That doesn't make sense, 'L' simulates the data read memory latency of an
SH[123].  movt doesn't incur such a latency.

> 	(trapa): Factor out duplicate variable 'imm' (same as 'i').

OK.  But I don't see why you need the cast to long.

> 	(sleep, trapa, ppi): Use SET_NIP to modify nip.

I don't see any need for this.  RAISE_EXCEPTION already clears
saved_state.asregs.insn_end , so that takes care of the
exceptions that might arise during sleep.
For trapa, that leaves just the possibility that we fail to miss a
loop bound that is set to somewhere inside a profiler trap; I think
you deserve whatever you get when you do that.
Similar for ppi; are you afrais that we fail to miss a loop bound
that is set to field_b of a ppi insn?


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 21:56 Michael Snyder
2004-02-12 22:39 ` Joern Rennecke [this message]
2004-02-12 23:52   ` Michael Snyder
2004-02-13 12:29     ` Joern Rennecke
2004-02-13 19:17       ` Michael Snyder
2004-02-14  4:48         ` 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=200402122239.i1CMdJK12072@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