From: Alex Coplan <alex.coplan@arm.com>
To: binutils@sourceware.org
Cc: Richard Earnshaw <rearnsha@arm.com>
Subject: [PATCH 1/2] aarch64: Add support for Neoverse N2 CPU
Date: Wed, 23 Sep 2020 14:45:51 +0100 [thread overview]
Message-ID: <20200923134551.wmtooduinx6hb2nw@arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
This patch adds support for Arm's Neoverse N2 CPU to AArch64 binutils.
Testing:
* Regression tested on aarch64-none-elf.
OK for master?
Thanks,
Alex
---
gas/ChangeLog:
2020-09-23 Alex Coplan <alex.coplan@arm.com>
* config/tc-aarch64.c (aarch64_cpus): Add neoverse-n2.
* doc/c-aarch64.texi: Document support for Neoverse N2.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1174 bytes --]
diff --git a/gas/config/tc-aarch64.c b/gas/config/tc-aarch64.c
index 57a2b4e997c..2e3d8d236db 100644
--- a/gas/config/tc-aarch64.c
+++ b/gas/config/tc-aarch64.c
@@ -8977,6 +8977,16 @@ static const struct aarch64_cpu_option_table aarch64_cpus[] = {
{"xgene2", AARCH64_FEATURE (AARCH64_ARCH_V8,
AARCH64_FEATURE_CRC), "APM X-Gene 2"},
{"cortex-r82", AARCH64_ARCH_V8_R, "Cortex-R82"},
+ {"neoverse-n2", AARCH64_FEATURE (AARCH64_ARCH_V8_5,
+ AARCH64_FEATURE_BFLOAT16
+ | AARCH64_FEATURE_I8MM
+ | AARCH64_FEATURE_F16
+ | AARCH64_FEATURE_SVE
+ | AARCH64_FEATURE_SVE2
+ | AARCH64_FEATURE_SVE2_BITPERM
+ | AARCH64_FEATURE_MEMTAG
+ | AARCH64_FEATURE_RNG),
+ "Neoverse N2"},
{"generic", AARCH64_ARCH_V8, NULL},
{NULL, AARCH64_ARCH_NONE, NULL}
diff --git a/gas/doc/c-aarch64.texi b/gas/doc/c-aarch64.texi
index d8f2e19326f..67c299a8790 100644
--- a/gas/doc/c-aarch64.texi
+++ b/gas/doc/c-aarch64.texi
@@ -72,6 +72,7 @@ on the target processor. The following processor names are recognized:
@code{exynos-m1},
@code{falkor},
@code{neoverse-n1},
+@code{neoverse-n2},
@code{neoverse-e1},
@code{qdf24xx},
@code{saphira},
next reply other threads:[~2020-09-23 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 13:45 Alex Coplan [this message]
2020-09-28 9:17 ` Tamar Christina
2020-09-29 14:26 ` Alex Coplan
2020-09-29 15:24 ` Nick Clifton
2020-09-30 11:23 ` Alex Coplan
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=20200923134551.wmtooduinx6hb2nw@arm.com \
--to=alex.coplan@arm.com \
--cc=binutils@sourceware.org \
--cc=rearnsha@arm.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).