From: Joseph Myers <joseph@codesourcery.com>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Cc: Umesh Kalappa <umesh.kalappa0@gmail.com>, <bug-binutils@gnu.org>,
Binutils <binutils@sourceware.org>
Subject: Re: ARMV7a: selected processor does not support requested special purpose register
Date: Tue, 4 Oct 2022 15:10:34 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2210041508040.850856@digraph.polyomino.org.uk> (raw)
In-Reply-To: <06ca8cae-954d-0e34-58d2-7aa45d2f2579@foss.arm.com>
On Tue, 4 Oct 2022, Richard Earnshaw via Binutils wrote:
> You won't find (well are extremely unlikely to find) any documentation for the
> legacy mnemonics online - the reference I have is from the ARMv5 ARM ARM from
> nearly 20 years ago, which was in paper form.
It seems DDI0100I (v6 ARM) is still online:
https://documentation-service.arm.com/static/5f8dacc8f86e16515cdb865a
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2022-10-04 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 14:41 Umesh Kalappa
2022-10-03 15:48 ` Richard Earnshaw
2022-10-03 15:54 ` Richard Earnshaw
2022-10-04 4:26 ` Umesh Kalappa
2022-10-04 10:03 ` Richard Earnshaw
2022-10-04 15:10 ` Joseph Myers [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=alpine.DEB.2.22.394.2210041508040.850856@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=binutils@sourceware.org \
--cc=bug-binutils@gnu.org \
--cc=umesh.kalappa0@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).