Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joern Rennecke <joern.rennecke@superh.com>
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com, ezannoni@redhat.com, bje@redhat.com
Subject: [Fwd: Re: Enum constants for sh1-sh4, sh{3}-dsp register numbers in  thesimulator]
Date: Thu, 23 May 2002 08:41:00 -0000	[thread overview]
Message-ID: <3CED0B5C.7281676D@superh.com> (raw)

I'm still wainting for an answer to my questions here.

Andrew Cagney wrote:
> 
> > Index: include/gdb/sim-sh.h
> > ===================================================================
> > RCS file: /cvs/src/src/include/gdb/sim-sh.h,v
> > retrieving revision 1.1
> One thought.
> 
> This is a true enum and not a bunch of constants.  Perhaphs it would be
> better to simply list all the enum members.

Do you mean to add  SIM_SH_FR1_REGNUM .. SIM_SH_FR15_REGNUM and the various
individual banked regnums?  I could do that.

OTOH, if you mean to remove the seed values like 24 for SIM_SH_DSR_REGNUM and
40 for SIM_SH_MOD_REGNUM, making a flat enum, that would break backwards
compatibility,
as we have some gaps, and overlaps between floating point and dsp registers.
(This mirrors an overlap in the instruction set.  In fact the instructions to
manipulate
 FPSCR and DSR are the same, and the simulator makes use of this by treating
them really
 as the same.)
	
-- 
--------------------------
SuperH
2430 Aztec West / Almondsbury / BRISTOL / BS32 4AQ
T:+44 1454 462330


             reply	other threads:[~2002-05-23 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-23  8:41 Joern Rennecke [this message]
2002-05-23  9:07 ` Andrew Cagney
2002-05-23 11:49   ` [Fwd: Re: Enum constants for sh1-sh4, sh{3}-dsp register numbersin thesimulator] 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=3CED0B5C.7281676D@superh.com \
    --to=joern.rennecke@superh.com \
    --cc=ac131313@cygnus.com \
    --cc=bje@redhat.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