From: Elena Zannoni <ezannoni@redhat.com>
To: Joern Rennecke <joern.rennecke@superh.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Unreviewed patches
Date: Tue, 02 Jul 2002 12:32:00 -0000 [thread overview]
Message-ID: <15649.65211.660582.965251@localhost.redhat.com> (raw)
In-Reply-To: <3D20D12F.6AB9E865@superh.com>
Joern Rennecke writes:
> Elena Zannoni wrote:
> > OK, I see what you are saying, but I don't think that removing the overlaps
> > from the gdb<->sim interface necessarily forces you to remove the overlaps
> > from inside the simulator.
>
> You have a point here. The translation is quite arbitrary.
>
> > It just cleans up the sim_fetch_register and sim_store_register code.
>
> It also changes the interface.
>
> > I am not sure I understand your claim about compatibility. You mean
> > older gdb's with new sims? That cannot happen. Or you mean the layout
>
> Older gdb's with new sims, or older sims with new gdb's.
>
Hmm, I don't think we ever worried about that. We have broken
compatibility even between gcc and gdb, sometimes. And here the chance
is smaller, given that sim and gdb come from the same repo and are
built and linked together.
> Why should it be safe to have different register numbers in the interface
> to the same simulator of a slightly different vintage, yet unsafe to
> have different meanings for the same register numbers in the sh vs. sh64
> simulator?
>
I think that this is the opportunity to create a clean(er) interface,
and we should do it right. (I was actually commenting on the sh
numbering, not the sh64 yet).
BTW, there is an example of gdb-to-sim-regnum translation in the d10v:
d10v_ts2_register_sim_regno and d10v_ts3_register_sim_regno.
> > > > I think the changes below depend on the cgen patches being accepted first.
> > >
> > > They have.
> > >
> >
> > I don't see any replies to your message to the cgen/gdb-patches lists.
>
> Still, when you look at ChangeLog and cpu/{sh64-compact.cpu,sh64-media.cpu},
> you'll see that Ben Elliston has applied my patch.
>
Oh, yes, I see them. I guess they don't reply with 'accepted' in the
cgen world.
But I cannot approve changes to the sh64 sim.
Elena
> --
> --------------------------
> SuperH
> 2430 Aztec West / Almondsbury / BRISTOL / BS32 4AQ
> T:+44 1454 462330
next prev parent reply other threads:[~2002-07-02 19:32 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
2002-07-01 14:24 ` Elena Zannoni
2002-07-01 15:01 ` Joern Rennecke
2002-07-02 12:32 ` Elena Zannoni [this message]
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=15649.65211.660582.965251@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=joern.rennecke@superh.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