From: Richard Earnshaw <rearnsha@arm.com>
To: Ben Harris <bjh21@netbsd.org>
Cc: gdb-patches@sourceware.cygnus.com, Richard.Earnshaw@arm.com
Subject: Re: Fix arm_addr_bits_remove: 26-bit Thumb doesn't exist
Date: Sat, 20 Oct 2001 10:46:00 -0000 [thread overview]
Message-ID: <200110201746.SAA12334@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: <Pine.SOL.4.33.0110201758490.17268-100000@virgo.cus.cam.ac.uk>
> I haven't actually encountered this bug in reality yet, but it looks to me
> as if arm_addr_bits_remove() is bogus. Specifically, it has a case for
> Thumb state in a 26-bit mode. According to the ARM ARM (2nd Edition,
> section A8.1), no processor will support both 26-bit mode and thumb state
> at all, let alone at the same time. I suspect this might be a noticable
> problem when debugging SVC mode code, since then R15 will have its bottom
> bit set, which arm_pc_is_thumb() is likely to interpret as meaning the CPU
> is in Thumb state.
Yep, I agree. And also for your earlier patch.
R.
prev parent reply other threads:[~2001-10-20 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-20 10:23 Ben Harris
2001-10-20 10:46 ` Richard Earnshaw [this message]
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=200110201746.SAA12334@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=bjh21@netbsd.org \
--cc=gdb-patches@sourceware.cygnus.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