From: Alex Coplan <alex.coplan@arm.com>
To: binutils@sourceware.org
Cc: Richard Earnshaw <rearnsha@arm.com>
Subject: [PATCH 2/2] arm: Add support for Neoverse N2 CPU
Date: Wed, 23 Sep 2020 14:47:02 +0100 [thread overview]
Message-ID: <20200923134702.in3zbmo47edff3rz@arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
This adds support for Arm's Neoverse N2 CPU to AArch32 binutils. The
Neoverse N2 CPU builds AArch32 at EL0 and therefore needs support in the
AArch32 assembler.
Testing:
* Regression tested on arm-none-eabi.
OK for master?
Thanks,
Alex
---
gas/ChangeLog:
2020-09-23 Alex Coplan <alex.coplan@arm.com>
* config/tc-arm.c (arm_cpus): Add Neoverse N2.
* doc/c-arm.texi: Document -mcpu=neoverse-n2.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1098 bytes --]
diff --git a/gas/config/tc-arm.c b/gas/config/tc-arm.c
index 32feaa1ca09..fce3ad36e0a 100644
--- a/gas/config/tc-arm.c
+++ b/gas/config/tc-arm.c
@@ -31594,6 +31594,11 @@ static const struct arm_cpu_option_table arm_cpus[] =
ARM_CPU_OPT ("neoverse-n1", "Neoverse N1", ARM_ARCH_V8_2A,
ARM_FEATURE_CORE_HIGH (ARM_EXT2_FP16_INST),
FPU_ARCH_CRYPTO_NEON_VFP_ARMV8_DOTPROD),
+ ARM_CPU_OPT ("neoverse-n2", "Neoverse N2", ARM_ARCH_V8_5A,
+ ARM_FEATURE_CORE_HIGH (ARM_EXT2_FP16_INST
+ | ARM_EXT2_BF16
+ | ARM_EXT2_I8MM),
+ FPU_ARCH_CRYPTO_NEON_VFP_ARMV8_4),
/* ??? XSCALE is really an architecture. */
ARM_CPU_OPT ("xscale", NULL, ARM_ARCH_XSCALE,
ARM_ARCH_NONE,
diff --git a/gas/doc/c-arm.texi b/gas/doc/c-arm.texi
index 91803605775..39e24e71af0 100644
--- a/gas/doc/c-arm.texi
+++ b/gas/doc/c-arm.texi
@@ -151,6 +151,7 @@ recognized:
@code{marvell-pj4},
@code{marvell-whitney},
@code{neoverse-n1},
+@code{neoverse-n2},
@code{xgene1},
@code{xgene2},
@code{ep9312} (ARM920 with Cirrus Maverick coprocessor),
next reply other threads:[~2020-09-23 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 13:47 Alex Coplan [this message]
2020-09-23 17:27 ` Ramana Radhakrishnan
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=20200923134702.in3zbmo47edff3rz@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).