From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Richard.Earnshaw@arm.com, gdb@sources.redhat.com
Subject: Re: ARM and virtual/raw registers
Date: Mon, 13 May 2002 06:18:00 -0000 [thread overview]
Message-ID: <200205131317.OAA03301@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Mon, 13 May 2002 09:13:23 EDT." <3CDFBBF3.7080700@cygnus.com>
> >
> > OK, I'm trying this general approach. One major failure, unfortunately.
> >
> > The remote-sim code has:
> >
> > else if (REGISTER_NAME (regno) != NULL
> > && *REGISTER_NAME (regno) != '\0')
> > {
> > char buf[MAX_REGISTER_RAW_SIZE];
> > int nr_bytes;
> > if (REGISTER_SIM_REGNO (regno) >= 0)
> > nr_bytes = sim_fetch_register (gdbsim_desc,
> > REGISTER_SIM_REGNO (regno),
> > buf, REGISTER_RAW_SIZE (regno));
> > ...
> > supply_register (regno, buf);
> >
> > Which is precisely the opposite of what I want: sim_fetch_register needs
> > to fetch the raw (uncooked) registers, which is precisely the set that
> > don't have names :-(
> >
> > REGISTER_SIM_REGNO doesn't help, because we never get to the code for the
> > registers I need.
>
> Want it fixed? Next to no targets define the macro so changing the the
> behavour - make REGISTER_SIM_REGNO totally responsible for the decision
> is straight forward.
>
> (In fact, why didn't I do this before).
Yeah! that would be great.
R.
next prev parent reply other threads:[~2002-05-13 13:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 7:31 Richard Earnshaw
2002-05-09 9:45 ` Andrew Cagney
2002-05-09 10:01 ` Richard Earnshaw
2002-05-09 11:52 ` Andrew Cagney
2002-05-10 3:45 ` Richard Earnshaw
2002-05-10 7:48 ` Andrew Cagney
2002-05-10 12:07 ` Andrew Cagney
2002-05-11 7:05 ` Richard Earnshaw
2002-05-11 14:52 ` Andrew Cagney
2002-05-12 7:20 ` Richard Earnshaw
2002-05-12 8:25 ` Andrew Cagney
2002-05-12 8:30 ` Richard Earnshaw
2002-05-12 8:51 ` Andrew Cagney
2002-05-10 9:29 ` Richard Earnshaw
2002-05-10 11:42 ` Andrew Cagney
2002-05-11 6:16 ` Richard Earnshaw
2002-05-11 11:41 ` Richard Earnshaw
2002-05-11 13:36 ` Andrew Cagney
2002-05-12 7:11 ` Richard Earnshaw
2002-05-12 7:40 ` Richard Earnshaw
2002-05-12 9:03 ` Andrew Cagney
2002-05-12 11:31 ` Andrew Cagney
2002-05-12 8:07 ` Andrew Cagney
2002-05-12 8:25 ` Richard Earnshaw
2002-05-12 8:41 ` Andrew Cagney
2002-05-13 5:35 ` Richard Earnshaw
2002-05-13 6:13 ` Andrew Cagney
2002-05-13 6:18 ` Richard Earnshaw [this message]
2002-05-09 10:08 ` Andrew Cagney
2002-05-09 10:36 ` Richard Earnshaw
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=200205131317.OAA03301@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=gdb@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