From: Andrew Cagney <cagney@gnu.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: make sim interface use gdbarch methods for collect/supply
Date: Fri, 02 Jul 2004 15:19:00 -0000 [thread overview]
Message-ID: <40E57CDF.8090809@gnu.org> (raw)
In-Reply-To: <vt2vfh9avzo.fsf@zenia.home>
> At the moment, remote-sim.c's gdbsim_fetch_register and
> gdbsim_store_register functions assume that the simulator's register
> set (as visible via sim_fetch_register and sim_store_register)
> corresponds exactly to GDB's raw register set. This patch is meant to
> remove that assumption.
Why do we need this extra level of indirection? Since gdb/sim are
paired at the source code level, we can simply change the gdb/sim interface.
Andrew
> 2004-06-30 Jim Blandy <jimb@redhat.com>
>
> Don't assume that the sim's register set and GDB's raw register
> set have the same layout.
> * gdbarch.sh (sim_supply_register, sim_collect_register): New
> methods. Have gdbarch.c #include regcache.h.
> * gdbarch.c, gdbarch.h: Regenerate.
> * remote-sim.c (gdbsim_fetch_register): Pass the register value
> collected from the sim to GDB via the new gdbarch methods.
> * Makefile.in (gdbarch.o): Update dependencies.
>
next prev parent reply other threads:[~2004-07-02 15:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 15:48 Jim Blandy
2004-06-30 15:53 ` Daniel Jacobowitz
2004-06-30 17:00 ` Jim Blandy
2004-07-01 2:48 ` Daniel Jacobowitz
2004-07-01 17:23 ` Jim Blandy
2004-07-01 17:31 ` Daniel Jacobowitz
2004-07-01 18:45 ` Jim Blandy
2004-07-01 18:48 ` Daniel Jacobowitz
2004-07-02 15:39 ` Andrew Cagney
2004-07-06 15:38 ` Daniel Jacobowitz
2004-07-06 17:10 ` Jim Blandy
2004-07-06 17:17 ` Daniel Jacobowitz
2004-07-15 18:35 ` Jim Blandy
2004-07-16 15:01 ` Daniel Jacobowitz
2004-07-06 17:43 ` Andrew Cagney
2004-07-06 18:31 ` Daniel Jacobowitz
2004-07-02 15:19 ` Andrew Cagney [this message]
2004-07-02 22:13 ` Jim Blandy
2004-07-06 15:18 ` Andrew Cagney
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=40E57CDF.8090809@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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