From: Michael Snyder <msnyder@redhat.com>
To: cagney@redhat.com, gdb-patches@sources.redhat.com
Subject: [regcache] raw vs. cooked...
Date: Sat, 07 Jun 2003 00:57:00 -0000 [thread overview]
Message-ID: <3EE13867.1E530DE9@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 180 bytes --]
Andrew,
I suspect the test below is not valid for pseudo-registers, since they
may not have a location in the reg cache at all. Anyway, the change
makes sh4 work again.
Michael
[-- Attachment #2: regcache.diff --]
[-- Type: text/plain, Size: 1027 bytes --]
Index: regcache.c
===================================================================
RCS file: /cvs/src/src/gdb/regcache.c,v
retrieving revision 1.82
diff -p -r1.82 regcache.c
*** regcache.c 17 May 2003 05:59:58 -0000 1.82
--- regcache.c 7 Jun 2003 00:55:07 -0000
*************** init_regcache_descr (struct gdbarch *gdb
*** 235,241 ****
/* Sanity check. Confirm that there is agreement between the
regcache and the target's redundant REGISTER_BYTE (new targets
should not even be defining it). */
! for (i = 0; i < descr->nr_cooked_registers; i++)
{
if (REGISTER_BYTE_P ())
gdb_assert (descr->register_offset[i] == REGISTER_BYTE (i));
--- 235,241 ----
/* Sanity check. Confirm that there is agreement between the
regcache and the target's redundant REGISTER_BYTE (new targets
should not even be defining it). */
! for (i = 0; i < descr->nr_raw_registers; i++)
{
if (REGISTER_BYTE_P ())
gdb_assert (descr->register_offset[i] == REGISTER_BYTE (i));
next reply other threads:[~2003-06-07 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 0:57 Michael Snyder [this message]
2003-06-08 19:06 ` Andrew Cagney
2003-06-08 19:50 ` Kris Warkentin
2003-06-08 22:22 ` 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=3EE13867.1E530DE9@redhat.com \
--to=msnyder@redhat.com \
--cc=cagney@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