public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
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 V1 CPU
Date: Tue, 22 Sep 2020 15:01:36 +0100	[thread overview]
Message-ID: <20200922140136.lotymvo7e3d6k47b@arm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 317 bytes --]

This patch adds support for Arm's Neoverse V1 CPU to AArch32 binutils.

Testing:
 * Regression tested on arm-none-eabi.

OK for master?

Thanks,
Alex

---

gas/ChangeLog:

2020-09-22  Alex Coplan  <alex.coplan@arm.com>

	* config/tc-arm.c (arm_cpus): Add Neoverse V1.
	* doc/c-arm.texi: Document Neoverse V1 support.

[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 955 bytes --]

diff --git a/gas/config/tc-arm.c b/gas/config/tc-arm.c
index 5877847c3b9..ff9072795b1 100644
--- a/gas/config/tc-arm.c
+++ b/gas/config/tc-arm.c
@@ -31622,6 +31622,11 @@ static const struct arm_cpu_option_table arm_cpus[] =
 	       ARM_FEATURE_CORE_HIGH (ARM_EXT2_CRC),
 	       FPU_ARCH_CRYPTO_NEON_VFP_ARMV8),
 
+  /* Arm Neoverse V1.  */
+  ARM_CPU_OPT ("neoverse-v1", "Neoverse V1", ARM_ARCH_V8_4A,
+	       ARM_FEATURE_CORE_HIGH (ARM_EXT2_BF16 | ARM_EXT2_I8MM),
+	       FPU_ARCH_CRYPTO_NEON_VFP_ARMV8_4),
+
   { NULL, 0, ARM_ARCH_NONE, ARM_ARCH_NONE, ARM_ARCH_NONE, NULL }
 };
 #undef ARM_CPU_OPT
diff --git a/gas/doc/c-arm.texi b/gas/doc/c-arm.texi
index 91803605775..dde3ff75c80 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-v1},
 @code{xgene1},
 @code{xgene2},
 @code{ep9312} (ARM920 with Cirrus Maverick coprocessor),

             reply	other threads:[~2020-09-22 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 14:01 Alex Coplan [this message]
2020-09-24 13:34 ` Nick Clifton
2020-09-24 14:52   ` 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=20200922140136.lotymvo7e3d6k47b@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).