From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: [rfa/ppc] Make registers unsigned
Date: Mon, 08 Mar 2004 22:02:00 -0000 [thread overview]
Message-ID: <404CED58.4010205@gnu.org> (raw)
Message-ID: <20040308220200.R_DHzbFzf1AaoKG1W7VJlLglEnvnzjS5kpcgaLcsf-I@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 284 bytes --]
Hello,
As far as I can tell PPC registers are unsigned. At present they are
signed and this leads to weird problems such as:
(gdb) x/i $sp
0xffff0000: ... error accessing memory at 0xffff0000
(gdb) x/i 0xffff0000
0xffff0000: sc
(gdb)
the attached changes this.
ok, 6.1?
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 781 bytes --]
2004-03-07 Andrew Cagney <cagney@redhat.com>
* rs6000-tdep.c (rs6000_register_virtual_type): Make registers
unsigned.
Index: rs6000-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/rs6000-tdep.c,v
retrieving revision 1.183
diff -u -r1.183 rs6000-tdep.c
--- rs6000-tdep.c 2 Mar 2004 02:20:25 -0000 1.183
+++ rs6000-tdep.c 8 Mar 2004 21:56:35 -0000
@@ -1862,12 +1862,12 @@
case 0:
return builtin_type_int0;
case 4:
- return builtin_type_int32;
+ return builtin_type_uint32;
case 8:
if (tdep->ppc_ev0_regnum <= n && n <= tdep->ppc_ev31_regnum)
return builtin_type_vec64;
else
- return builtin_type_int64;
+ return builtin_type_uint64;
break;
case 16:
return builtin_type_vec128;
next reply other threads:[~2004-03-08 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Andrew Cagney [this message]
2004-03-08 22:02 ` Andrew Cagney
2004-03-15 18:25 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-15 19:51 ` Kevin Buettner
2004-03-19 0:09 ` Andrew Cagney
2004-03-15 21:21 ` Andrew Cagney
2004-03-19 0:09 ` Kevin Buettner
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=404CED58.4010205@gnu.org \
--to=cagney@gnu.org \
--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