Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joern Rennecke <joern.rennecke@st.com>
To: ac131313@cygnus.com
Cc: bje@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: SH5 simulator contribution
Date: Mon, 29 Apr 2002 10:23:00 -0000	[thread overview]
Message-ID: <3CCD81CD.CBAC3A62@st.com> (raw)
In-Reply-To: <3CBF73A3.2090409@cygnus.com>

ac131313@cygnus.com wrote:
> 
> > So I don't see that you gain anything by unifying the numbering scheme
> >> > in the gdb <-> sim interface, as it would be at odds with the interface
> >> > to gcc and the hardware interfaces.
> >
> >>
> >> Formalizing would be a better word.  So that GDB and the SIM can agree
> >> on the register numbers and their sizes without needing to know the
> >> others internals.
> >
> >
> > They only need to know if the program is for an sh5 or an earlier processor.
> > This information is readily available from the elf flags (the lower five bits
> Having just looked at a different target (similar problem), I think
> having a single file that assigns different number ranges to the sh4 vs
> sh64 registers would be best.  That would make it easy to detect things
> like trying to fetch an SH64 register from the SH4 sim.

Using the current raw / pseudo-register distinction, that would lead to funny
artifacts: the sh and sh64 raw registers would all come first, and only then
the can the pseudo registers follow.

In regcache.c:fetch_register / store_register, you added this comment:

   /* NOTE: cagney/2001-12-04: Legacy targets were using fetch/store
     pseudo-register as a way of handling registers that needed to be
     constructed from one or more raw registers.  New targets instead
     use gdbarch register read/write.  */

I suppose I could handle all the pseudos in sim_fetch_register /
sim_store_register,
but then the hardware interfaces would break.

So maybe for the pre-sh5 targets, we should continue to use a relatively low
raw register threshold so that the pseudo registers can immediately follow;
The sh64 simulator can use a higher threshold that makes the sh4 pseudos into
registers that are read/stored with sim_read_register / sim_store_register,
i.e. eventuially via sh64_fetch_register / sh64_store_register.
Then the sh1..sh4 register numbers can be used for the compact registers, too.

	
-- 
--------------------------
SuperH
2430 Aztec West / Almondsbury / BRISTOL / BS32 4AQ
T:+44 1454 462330


  reply	other threads:[~2002-04-29 17:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-02  2:06 Ben Elliston
2002-02-04 19:48 ` Andrew Cagney
2002-02-04 20:28   ` Ben Elliston
2002-02-04 20:59     ` Andrew Cagney
2002-02-04 22:29       ` Ben Elliston
2002-02-05  8:31         ` Andrew Cagney
2002-02-05 12:21           ` Ben Elliston
2002-02-05 17:36             ` Andrew Cagney
2002-04-12  2:46               ` Joern Rennecke
2002-04-12  9:30                 ` Andrew Cagney
2002-04-12  9:45                 ` Andrew Cagney
2002-04-15  1:48                   ` Joern Rennecke
2002-04-18 18:32                     ` Andrew Cagney
2002-04-29 10:23                       ` Joern Rennecke [this message]
2002-04-29 10:47                         ` Andrew Cagney
2002-04-29 11:30                           ` Joern Rennecke
2002-04-12  2:48               ` Joern Rennecke
2002-04-12  2:57               ` Joern Rennecke
2002-04-12  2:57               ` Joern Rennecke
2002-04-12  2:57               ` Joern Rennecke
2002-04-12  2:58               ` 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=3CCD81CD.CBAC3A62@st.com \
    --to=joern.rennecke@st.com \
    --cc=ac131313@cygnus.com \
    --cc=bje@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