public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] attribs: Use existing traits for excl_hash_traits
Date: Mon, 06 Nov 2023 12:32:27 +0000	[thread overview]
Message-ID: <mpth6lzawpw.fsf@arm.com> (raw)
In-Reply-To: <mptpm356emd.fsf@arm.com> (Richard Sandiford via Gcc-patches's message of "Tue, 29 Aug 2023 16:40:42 +0100")

Ping.

Richard Sandiford via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
> excl_hash_traits can be defined more simply by reusing existing traits.
>
> Tested on aarch64-linux-gnu.  OK to install?
>
> Richard
>
>
> gcc/
> 	* attribs.cc (excl_hash_traits): Delete.
> 	(test_attribute_exclusions): Use pair_hash and nofree_string_hash
> 	instead.
> ---
>  gcc/attribs.cc | 45 +++------------------------------------------
>  1 file changed, 3 insertions(+), 42 deletions(-)
>
> diff --git a/gcc/attribs.cc b/gcc/attribs.cc
> index b8cb55b97df..0d4ab23aeb6 100644
> --- a/gcc/attribs.cc
> +++ b/gcc/attribs.cc
> @@ -2640,47 +2640,6 @@ namespace selftest
>  
>  typedef std::pair<const char *, const char *> excl_pair;
>  
> -struct excl_hash_traits: typed_noop_remove<excl_pair>
> -{
> -  typedef excl_pair  value_type;
> -  typedef value_type compare_type;
> -
> -  static hashval_t hash (const value_type &x)
> -  {
> -    hashval_t h1 = htab_hash_string (x.first);
> -    hashval_t h2 = htab_hash_string (x.second);
> -    return h1 ^ h2;
> -  }
> -
> -  static bool equal (const value_type &x, const value_type &y)
> -  {
> -    return !strcmp (x.first, y.first) && !strcmp (x.second, y.second);
> -  }
> -
> -  static void mark_deleted (value_type &x)
> -  {
> -    x = value_type (NULL, NULL);
> -  }
> -
> -  static const bool empty_zero_p = false;
> -
> -  static void mark_empty (value_type &x)
> -  {
> -    x = value_type ("", "");
> -  }
> -
> -  static bool is_deleted (const value_type &x)
> -  {
> -    return !x.first && !x.second;
> -  }
> -
> -  static bool is_empty (const value_type &x)
> -  {
> -    return !*x.first && !*x.second;
> -  }
> -};
> -
> -
>  /* Self-test to verify that each attribute exclusion is symmetric,
>     meaning that if attribute A is encoded as incompatible with
>     attribute B then the opposite relationship is also encoded.
> @@ -2690,13 +2649,15 @@ struct excl_hash_traits: typed_noop_remove<excl_pair>
>  static void
>  test_attribute_exclusions ()
>  {
> +  using excl_hash_traits = pair_hash<nofree_string_hash, nofree_string_hash>;
> +
>    /* Iterate over the array of attribute tables first (with TI0 as
>       the index) and over the array of attribute_spec in each table
>       (with SI0 as the index).  */
>    const size_t ntables = ARRAY_SIZE (attribute_tables);
>  
>    /* Set of pairs of mutually exclusive attributes.  */
> -  typedef hash_set<excl_pair, false, excl_hash_traits> exclusion_set;
> +  typedef hash_set<excl_hash_traits> exclusion_set;
>    exclusion_set excl_set;
>  
>    for (size_t ti0 = 0; ti0 != ntables; ++ti0)

  reply	other threads:[~2023-11-06 12:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 15:40 Richard Sandiford
2023-11-06 12:32 ` Richard Sandiford [this message]
2023-11-10 20:28   ` Jeff Law

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=mpth6lzawpw.fsf@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.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).