From: Ben Harris <bjh21@netbsd.org>
To: <gdb@sources.redhat.com>
Subject: PC and PSR on 26-bit ARM
Date: Mon, 22 Oct 2001 17:27:00 -0000 [thread overview]
Message-ID: <Pine.SOL.4.33.0110230101130.17545-100000@virgo.cus.cam.ac.uk> (raw)
I'm trying to make GDB work happily on NetBSD/arm26, which runs on ancient
ARM processors, where the PC and PSR share R15. As far as I can tell, the
code in arm-linux-nat.c, when fetching registers subprocess on a 26-bit
CPU, puts the PC in registers[PC_REGNUM], and the PC+PSR in
registers[PS_REGNUM]. When putting registers back into the process, it
sets R15 (PC+PSR) from registers[PC_REGNUM] and ignores
registers[PS_REGNUM].
I suppose my question is: is this the intended behaviour? i.e. should I:
(1) do the same on NetBSD,
(2) accurately emulate a 32-bit CPU in 26-bit mode (splitting and
merging PC and PSR at the subprocess interface), or
(3) present GDB with the real state of the CPU?
I think my preference is for (2), since this saves complexity in the rest
of GDB.
--
Ben Harris <bjh21@netbsd.org>
Portmaster, NetBSD/arm26 <URL: http://www.netbsd.org/Ports/arm26/ >
next reply other threads:[~2001-10-22 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 17:27 Ben Harris [this message]
2001-10-23 1:35 ` Philip Blundell
2001-10-25 21:48 ` Andrew Cagney
2001-10-29 14:44 ` Ben Harris
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=Pine.SOL.4.33.0110230101130.17545-100000@virgo.cus.cam.ac.uk \
--to=bjh21@netbsd.org \
--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