From: Matthieu Longo <matthieu.longo@arm.com>
To: binutils@sourceware.org
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>,
Nick Clifton <nickc@redhat.com>
Subject: [PATCH][Binutils] aarch64: Enable Cortex-X3 CPU
Date: Wed, 13 Dec 2023 15:41:43 +0000 [thread overview]
Message-ID: <36deddd8-d923-4913-9773-740d85f76e72@arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
Hi,
This patch adds support for the Cortex-X3 CPU to binutils.
Gas regression testing for aarch64-none-linux-gnu target and found no
regressions.
Ok for binutils-master? I don't have commit access so I need someone to
commit on my behalf.
Regards,
Matthieu.
[-- Attachment #2: 18078 --]
[-- Type: text/plain, Size: 2549 bytes --]
diff --git a/bfd/cpu-aarch64.c b/bfd/cpu-aarch64.c
index 269177821bb7a4ace7e69d0a99b34137293b0b3b..8e44b31e8d212f15c500af9c7af66cf7938c7241 100644
--- a/bfd/cpu-aarch64.c
+++ b/bfd/cpu-aarch64.c
@@ -75,6 +75,7 @@ processors[] =
{ bfd_mach_aarch64, "cortex-a76ae" },
{ bfd_mach_aarch64, "cortex-a77" },
{ bfd_mach_aarch64, "cortex-a720" },
+ { bfd_mach_aarch64, "cortex-x3" },
{ bfd_mach_aarch64, "cortex-x4" },
};
diff --git a/gas/NEWS b/gas/NEWS
index af03fd172cf34e3149440803ee86d2121392292d..4c8d5946690cf2aa886c1463a7e9c53404ef7d6a 100644
--- a/gas/NEWS
+++ b/gas/NEWS
@@ -32,6 +32,8 @@
* Add support for Cortex-A720 for AArch64.
+* Add support for Cortex-X3 for AArch64.
+
* Add support for Cortex-X4 for AArch64.
* Add support for RISC-V T-Head extensions (XTheadVector, XTheadZvlsseg
diff --git a/gas/config/tc-aarch64.c b/gas/config/tc-aarch64.c
index 5646de781d4502c0aa434368f0603c11ee456966..b5ede33c584277749805155350cad37d150c258a 100644
--- a/gas/config/tc-aarch64.c
+++ b/gas/config/tc-aarch64.c
@@ -10189,6 +10189,8 @@ static const struct aarch64_cpu_option_table aarch64_cpus[] = {
SSBS, PROFILE), "Cortex-X1"},
{"cortex-x2", AARCH64_CPU_FEATURES (V9A, 4, BFLOAT16, I8MM, MEMTAG,
SVE2_BITPERM), "Cortex-X2"},
+ {"cortex-x3", AARCH64_CPU_FEATURES (V9A, 4, BFLOAT16, I8MM, MEMTAG,
+ SVE2_BITPERM), "Cortex-X3"},
{"cortex-x4", AARCH64_CPU_FEATURES (V9_2A, 3, MEMTAG, PROFILE,
SVE2_BITPERM), "Cortex-X4"},
{"generic", AARCH64_ARCH_FEATURES (V8A), NULL},
diff --git a/gas/doc/c-aarch64.texi b/gas/doc/c-aarch64.texi
index cbf06bf3ec6d1680c74aad3a1a9364721ae7ca34..2bfb98a4027acc09b331aa1937407517b27297bd 100644
--- a/gas/doc/c-aarch64.texi
+++ b/gas/doc/c-aarch64.texi
@@ -91,6 +91,7 @@ on the target processor. The following processor names are recognized:
@code{cortex-r82},
@code{cortex-x1},
@code{cortex-x2},
+@code{cortex-x3},
and
@code{cortex-x4}.
The special name @code{all} may be used to allow the assembler to accept
diff --git a/gas/testsuite/gas/aarch64/cpu-cortex-x3.d b/gas/testsuite/gas/aarch64/cpu-cortex-x3.d
new file mode 100644
index 0000000000000000000000000000000000000000..2ea793783be01f290076bf030d5f4c768b915ee1
--- /dev/null
+++ b/gas/testsuite/gas/aarch64/cpu-cortex-x3.d
@@ -0,0 +1,6 @@
+# name: Assemble and dump for cortex-x3 CPU
+# source: nop-asm.s
+# as: -mcpu=cortex-x3
+# objdump: -d -mcortex-x3
+
+#...
\ No newline at end of file
next reply other threads:[~2023-12-13 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 15:41 Matthieu Longo [this message]
2023-12-15 14:55 ` Nick Clifton
2023-12-15 15:55 ` Nick Clifton
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=36deddd8-d923-4913-9773-740d85f76e72@arm.com \
--to=matthieu.longo@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).