From: Andrew Cagney <ac131313@cygnus.com>
To: Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: ARM and virtual/raw registers
Date: Sun, 12 May 2002 09:03:00 -0000 [thread overview]
Message-ID: <3CDE926B.7020508@cygnus.com> (raw)
In-Reply-To: <200205121439.PAA00494@cam-mail2.cambridge.arm.com>
> rearnsha@arm.com said:
>
>> See the code below (which is very much a work-in-progress..., so
>> don't even expect it to compile ;-)
>
>
> Of course, there was a major flaw in the WIP code I just posted, that
> confuses what I was talking about in a significant way. The code for
> arm_register_read, should be:
(I guessed this :-)
> static void
> arm_register_read (struct gdbarch *gdbarch, int regno, char *buffer)
> {
> if (arm_register_info[regno].regcache != ARM_PHYS_NONE)
> /* Recover the register directly from the cache. */
> regcache_read (arm_register_info[regno].regcache, buffer);
> else
> arm_pseudo_register_read (gdbarch, regno, buffer);
> }
If I had my way, it would read:
> static void
> arm_register_read (struct gdbarch *gdbarch, struct pseudoreg *pseudo, char *buffer)
> {
> arm_pseudo_register_read (gdbarch, pseudo, buffer);
> }
however, that is a long way off (and, to be honest, I suspect the amount
of effort required would not give a reasonable return). In the mean
time, I recommend:
> static void
> arm_register_read (struct gdbarch *gdbarch, int regno, char *buffer)
> {
> gdb_assert (regno >= NUM_REGS && regno < NUM_REGS+NUM_PSEUDO_REGS);
> arm_pseudo_register_read (gdbarch, regno, buffer);
> }
Per, the other e-mail. Keeping the separation is very important. The
next person to work on the code won't know if they are looking at a
pseudo or raw register.
Having debugged code that used this approach, this this is very important.
enjoy,
Andrew
next prev parent reply other threads:[~2002-05-12 16:03 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 [this message]
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
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=3CDE926B.7020508@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Richard.Earnshaw@arm.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