From: Andrew Carlotti <andrew.carlotti@arm.com>
To: binutils@sourceware.org
Subject: [PATCH] aarch64: Include +predres2 in -march=armv8.9-a
Date: Fri, 19 Jan 2024 17:28:06 +0000 [thread overview]
Message-ID: <360ba77c-2b65-aab5-f73a-0b9432356ee9@e124511.cambridge.arm.com> (raw)
This matches the dependencies in the architecture, in LLVM, and even in the
original Binutils commit message that mistakenly included it only in armv9.4-a.
Ok for master and 2.42 branch?
diff --git a/include/opcode/aarch64.h b/include/opcode/aarch64.h
index 6f02f472fda04effec714a3d2dc95d344c584978..02ee0fc2566d500359a9e89de3dfb954100f63ce 100644
--- a/include/opcode/aarch64.h
+++ b/include/opcode/aarch64.h
@@ -306,6 +306,7 @@ enum aarch64_feature_bit {
| AARCH64_FEATBIT (X, PMUv3_SS) \
| AARCH64_FEATBIT (X, PMUv3_ICNTR) \
| AARCH64_FEATBIT (X, SEBEP) \
+ | AARCH64_FEATBIT (X, PREDRES2) \
)
#define AARCH64_ARCH_V9A_FEATURES(X) (AARCH64_FEATBIT (X, V9A) \
@@ -315,8 +316,7 @@ enum aarch64_feature_bit {
#define AARCH64_ARCH_V9_1A_FEATURES(X) AARCH64_ARCH_V8_6A_FEATURES (X)
#define AARCH64_ARCH_V9_2A_FEATURES(X) AARCH64_ARCH_V8_7A_FEATURES (X)
#define AARCH64_ARCH_V9_3A_FEATURES(X) AARCH64_ARCH_V8_8A_FEATURES (X)
-#define AARCH64_ARCH_V9_4A_FEATURES(X) (AARCH64_ARCH_V8_9A_FEATURES (X) \
- | AARCH64_FEATBIT (X, PREDRES2))
+#define AARCH64_ARCH_V9_4A_FEATURES(X) AARCH64_ARCH_V8_9A_FEATURES (X)
/* Architectures are the sum of the base and extensions. */
#define AARCH64_ARCH_V8A(X) (AARCH64_FEATBIT (X, V8) \
next reply other threads:[~2024-01-19 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 17:28 Andrew Carlotti [this message]
2024-01-22 16:54 ` 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=360ba77c-2b65-aab5-f73a-0b9432356ee9@e124511.cambridge.arm.com \
--to=andrew.carlotti@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).