public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Richard Sandiford <richard.sandiford@arm.com>, binutils@sourceware.org
Subject: Re: [PATCH 2/2] aarch64: Allow feature flags to occupy >64 bits
Date: Tue, 26 Sep 2023 14:52:09 +0100	[thread overview]
Message-ID: <8aaea9fb-388c-210d-f240-d6a8c37db78f@arm.com> (raw)
In-Reply-To: <20230925202647.2049600-3-richard.sandiford@arm.com>

On 25/09/2023 21:26, Richard Sandiford via Binutils wrote:
> Following on from the previous patch to make the feature macros take
> a word number, this one increases the number of flag words from 1 to 2.
> 
> The patch uses some dummy features to push the number of features
> over 64.  The intention is that these should be reused by real
> features rather than kept as-is.
> ---
>  include/opcode/aarch64.h | 62 +++++++++++++++++++++++++---------------
>  1 file changed, 39 insertions(+), 23 deletions(-)

OK.

R.

> 
> diff --git a/include/opcode/aarch64.h b/include/opcode/aarch64.h
> index 54ac1d85fd4..ab42acac8c2 100644
> --- a/include/opcode/aarch64.h
> +++ b/include/opcode/aarch64.h
> @@ -158,7 +158,11 @@ enum aarch64_feature_bit {
>    /* Common Short Sequence Compression instructions.  */
>    AARCH64_FEATURE_CSSC,
>    /* SME2.  */
> -  AARCH64_FEATURE_SME2
> +  AARCH64_FEATURE_SME2,
> +  DUMMY1,
> +  DUMMY2,
> +  DUMMY3,
> +  AARCH64_NUM_FEATURES
>  };
>  
>  /* These macros take an initial argument X that gives the index into
> @@ -257,50 +261,61 @@ enum aarch64_feature_bit {
>  #define AARCH64_ARCH_NONE(X)	0
>  
>  /* CPU-specific features.  */
> -typedef unsigned long long aarch64_feature_set;
> +typedef struct {
> +  uint64_t flags[(AARCH64_NUM_FEATURES + 63) / 64];
> +} aarch64_feature_set;
>  
>  #define AARCH64_CPU_HAS_FEATURE(CPU,FEAT)	\
> -  ((~(CPU) & AARCH64_FEATBIT (0, FEAT)) == 0)
> +  ((~(CPU).flags[0] & AARCH64_FEATBIT (0, FEAT)) == 0		\
> +   && (~(CPU).flags[1] & AARCH64_FEATBIT (1, FEAT)) == 0)
>  
>  #define AARCH64_CPU_HAS_ALL_FEATURES(CPU,FEAT)	\
> -  ((~(CPU) & (FEAT)) == 0)
> +  ((~(CPU).flags[0] & (FEAT).flags[0]) == 0	\
> +   && (~(CPU).flags[1] & (FEAT).flags[1]) == 0)
>  
>  #define AARCH64_CPU_HAS_ANY_FEATURES(CPU,FEAT)	\
> -  (((CPU) & (FEAT)) != 0)
> +  (((CPU).flags[0] & (FEAT).flags[0]) != 0	\
> +   || ((CPU).flags[1] & (FEAT).flags[1]) != 0)
>  
>  #define AARCH64_SET_FEATURE(DEST, FEAT) \
> -  ((DEST) = FEAT (0))
> +  ((DEST).flags[0] = FEAT (0),		\
> +   (DEST).flags[1] = FEAT (1))
>  
>  #define AARCH64_CLEAR_FEATURE(DEST, SRC, FEAT)		\
> -  ((DEST) = (SRC) & ~AARCH64_FEATBIT (0, FEAT))
> -
> -#define AARCH64_MERGE_FEATURE_SETS(TARG,F1,F2)	\
> -  do						\
> -    {						\
> -      (TARG) = (F1) | (F2);			\
> -    }						\
> +  ((DEST).flags[0] = (SRC).flags[0] & ~AARCH64_FEATBIT (0, FEAT), \
> +   (DEST).flags[1] = (SRC).flags[1] & ~AARCH64_FEATBIT (1, FEAT))
> +
> +#define AARCH64_MERGE_FEATURE_SETS(TARG,F1,F2)		\
> +  do							\
> +    {							\
> +      (TARG).flags[0] = (F1).flags[0] | (F2).flags[0];	\
> +      (TARG).flags[1] = (F1).flags[1] | (F2).flags[1];	\
> +    }							\
>    while (0)
>  
> -#define AARCH64_CLEAR_FEATURES(TARG,F1,F2)	\
> -  do						\
> -    { 						\
> -      (TARG) = (F1) &~ (F2);			\
> -    }						\
> +#define AARCH64_CLEAR_FEATURES(TARG,F1,F2)		\
> +  do							\
> +    {							\
> +      (TARG).flags[0] = (F1).flags[0] &~ (F2).flags[0];	\
> +      (TARG).flags[1] = (F1).flags[1] &~ (F2).flags[1];	\
> +    }							\
>    while (0)
>  
>  /* aarch64_feature_set initializers for no features and all features,
>     respectively.  */
> -#define AARCH64_NO_FEATURES 0
> -#define AARCH64_ALL_FEATURES -1
> +#define AARCH64_NO_FEATURES { { 0, 0 } }
> +#define AARCH64_ALL_FEATURES { { -1, -1 } }
>  
>  /* An aarch64_feature_set initializer for a single feature,
>     AARCH64_FEATURE_<FEAT>.  */
> -#define AARCH64_FEATURE(FEAT) AARCH64_FEATBIT (0, FEAT)
> +#define AARCH64_FEATURE(FEAT) \
> +  { { AARCH64_FEATBIT (0, FEAT), AARCH64_FEATBIT (1, FEAT) } }
>  
>  /* An aarch64_feature_set initializer for a specific architecture version,
>     including all the features that are enabled by default for that architecture
>     version.  */
> -#define AARCH64_ARCH_FEATURES(ARCH) AARCH64_ARCH_##ARCH (0)
> +#define AARCH64_ARCH_FEATURES(ARCH) \
> +  { { AARCH64_ARCH_##ARCH (0), AARCH64_ARCH_##ARCH (1) } }
>  
>  /* Used by AARCH64_CPU_FEATURES.  */
>  #define AARCH64_OR_FEATURES_1(X, ARCH, F1) \
> @@ -325,7 +340,8 @@ typedef unsigned long long aarch64_feature_set;
>  /* An aarch64_feature_set initializer for a CPU that implements architecture
>     version ARCH, and additionally provides the N features listed in "...".  */
>  #define AARCH64_CPU_FEATURES(ARCH, N, ...)			\
> -  AARCH64_OR_FEATURES_##N (0, ARCH, __VA_ARGS__)
> +  { { AARCH64_OR_FEATURES_##N (0, ARCH, __VA_ARGS__),		\
> +      AARCH64_OR_FEATURES_##N (1, ARCH, __VA_ARGS__) } }
>  
>  /* An aarch64_feature_set initializer for the N features listed in "...".  */
>  #define AARCH64_FEATURES(N, ...) \


      reply	other threads:[~2023-09-26 13:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 20:26 [PATCH 0/2] aarch64: Restructure feature flag handling Richard Sandiford
2023-09-25 20:26 ` [PATCH 1/2] " Richard Sandiford
2023-09-26 10:23   ` Richard Earnshaw (lists)
2023-09-26 13:35     ` Richard Sandiford
2023-09-26 13:47       ` Richard Earnshaw (lists)
2023-09-25 20:26 ` [PATCH 2/2] aarch64: Allow feature flags to occupy >64 bits Richard Sandiford
2023-09-26 13:52   ` Richard Earnshaw (lists) [this message]

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=8aaea9fb-388c-210d-f240-d6a8c37db78f@arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=binutils@sourceware.org \
    --cc=richard.sandiford@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).