From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: Binutils <binutils@sourceware.org>
Subject: [PATCH] aarch64: Remove support for CSRE
Date: Mon, 11 Jan 2021 09:59:16 +0000 [thread overview]
Message-ID: <DB7PR08MB3002ABA83C76ECD8BE3A102193AB0@DB7PR08MB3002.eurprd08.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]
[apologies for resending, now compressed the attachment]
Hi all,
This patch removes support for the CSRE extension from aarch64 gas/objdump.
CSRE (FEAT_CSRE) is part of the Future Architecture Technologies program and at this time
Arm is withdrawing this particular feature:
https://developer.arm.com/architectures/cpu-architecture/a-profile/exploration-tools/future-architecture-technologies-a64-instruction-set-architecture
The patch removes the system registers and the CSR PDEC instruction.
Apologies for the late patch so close to release.
Tested make check-gas on aarch64-none-elf.
Ok for master and the 2.26 branch?
Thanks,
Kyrill
gas/ChangeLog
* NEWS: Remove CSRE.
* config/tc-aarch64.c (parse_csr_operand): Delete.
(parse_operands): Delete handling of AARCH64_OPND_CSRE_CSR.
(aarch64_features): Remove csre.
* doc/c-aarch64.texi: Remove CSRE.
* testsuite/gas/aarch64/csre.d: Delete.
* testsuite/gas/aarch64/csre-invalid.s: Likewise.
* testsuite/gas/aarch64/csre-invalid.d: Likewise.
* testsuite/gas/aarch64/csre_csr.s: Likewise.
* testsuite/gas/aarch64/csre_csr.d: Likewise.
* testsuite/gas/aarch64/csre_csr-invalid.s: Likewise.
* testsuite/gas/aarch64/csre_csr-invalid.l: Likewise.
* testsuite/gas/aarch64/csre_csr-invalid.d: Likewise.
include/ChangeLog
* opcode/aarch64.h (AARCH64_FEATURE_CSRE): Delete.
(aarch64_opnd): Delete AARCH64_OPND_CSRE_CSR.
opcodes/ChangeLog
* aarch64-asm-2.c: Regenerate.
* aarch64-dis-2.c: Likewise.
* aarch64-opc-2.c: Likewise.
* aarch64-opc.c (aarch64_print_operand): Delete handling of AARCH64_OPND_CSRE_CSR.
* aarch64-tbl.h (aarch64_feature_csre): Delete.
(CSRE): Likewise.
(_CSRE_INSN): Likewise.
(aarch64_opcode_table): Delete csr.
[-- Attachment #2: csre.patch.bz2 --]
[-- Type: application/octet-stream, Size: 26657 bytes --]
next reply other threads:[~2021-01-11 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 9:59 Kyrylo Tkachov [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-11 9:48 Kyrylo Tkachov
2021-01-11 13:47 ` Nick Clifton
2021-01-11 15:08 ` Kyrylo Tkachov
2021-01-12 11:37 ` Nick Clifton
2021-01-12 12:39 ` H.J. Lu
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=DB7PR08MB3002ABA83C76ECD8BE3A102193AB0@DB7PR08MB3002.eurprd08.prod.outlook.com \
--to=kyrylo.tkachov@arm.com \
--cc=binutils@sourceware.org \
/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).