From: Joern Rennecke <joern.rennecke@superh.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Unreviewed patches
Date: Mon, 01 Jul 2002 10:10:00 -0000 [thread overview]
Message-ID: <3D208CF1.AB7AC45A@superh.com> (raw)
In-Reply-To: <15648.31077.572892.886182@localhost.redhat.com>
Elena Zannoni wrote:
>
> Joern Rennecke writes:
> > Wed Jun 12 13:20:51 2002 J"orn Rennecke <joern.rennecke@superh.com>
> >
> > include/gdb:
> > * sim-sh.h: Add enum constants for sh[1-4], sh3e, sh3?-dsp.
>
> Yes, sorry for the delay.
>
> Is there any real reason to not just have one enum, which included the
> dsp registers as well?
Yes. The values are supposed to stay the same, to retain compatibility.
Besides, you would need to re-design parts of the simulator to remove
the overlaps.
> I mean, if the simulator didn't reuse register
> numbers for FP regs and DPS regs, then you could get rid of this ugly
> code in interp.c:
>
> else case 44:
> if (target_dsp)
> RE = val;
> else case 45: case 46: case 47: case 48: case 49: case 50:
> [...]
> case 26:
> val = target_dsp ? A0 : FI (1);
> break;
> [...]
> etc. etc.
>
> And with that you could get rid of the target_dsp variable.
Definitely not. The same 0xfxxx opcodes mean different things to sh3-dsp
and sh3e.
Using the same register number for fpscr and dsr is natural, since the same
opcodes are used to load/store dsr on sh3-dsp and fpscr on sh3e.
> I think the changes below depend on the cgen patches being accepted first.
They have.
--
--------------------------
SuperH
2430 Aztec West / Almondsbury / BRISTOL / BS32 4AQ
T:+44 1454 462330
next prev parent reply other threads:[~2002-07-01 17:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 6:55 Joern Rennecke
2002-07-01 8:47 ` Elena Zannoni
2002-07-01 10:10 ` Joern Rennecke [this message]
2002-07-01 14:24 ` Elena Zannoni
2002-07-01 15:01 ` Joern Rennecke
2002-07-02 12:32 ` Elena Zannoni
2002-07-03 13:49 ` Joern Rennecke
2002-07-12 4:59 ` Elena Zannoni
2002-07-12 5:47 ` Joern Rennecke
2002-07-12 8:23 ` Andrew Cagney
2002-07-17 11:30 ` Joern Rennecke
2002-07-17 13:04 ` Andrew Cagney
2002-08-05 6:47 ` Elena Zannoni
2002-07-12 11:36 ` Elena Zannoni
-- strict thread matches above, loose matches on Subject: below --
2007-10-11 14:51 Kazu Hirata
2007-10-04 12:04 Kazu Hirata
2003-01-30 6:03 Kazu Hirata
2003-01-31 2:36 ` Michael Snyder
2003-01-31 4:54 ` Kazu Hirata
2003-02-01 1:27 ` Michael Snyder
2003-02-01 3:23 ` Kazu Hirata
2003-02-03 20:30 ` Michael Snyder
2003-02-03 23:30 ` Kazu Hirata
2003-02-05 22:41 ` Michael Snyder
2003-01-17 4:33 Kazu Hirata
2002-06-19 14:29 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=3D208CF1.AB7AC45A@superh.com \
--to=joern.rennecke@superh.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@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