public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: GCC patches <gcc-patches@gcc.gnu.org>,
	Andrew MacLeod <amacleod@redhat.com>
Subject: Re: [PATCH] Abstract out calculation of max HWIs per wide int.
Date: Mon, 17 Apr 2023 11:47:58 -0700	[thread overview]
Message-ID: <CA+=Sn1=cBQ3V-SsXwcLVMoSL89-uGY0p8tGGOQdGUgJ_xeyxpA@mail.gmail.com> (raw)
In-Reply-To: <20230417183917.216257-1-aldyh@redhat.com>

On Mon, Apr 17, 2023 at 11:44 AM Aldy Hernandez via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> I'm about to add one more use of the same snippet of code, for a total
> of 4 identical calculations in the code base.
>
> This seems safe enough even before the release, since this file hardly
> changes and I'm pretty much the only one who's touched it this year.
>
> OK for trunk?
>
> gcc/ChangeLog:
>
>         * wide-int.h (WIDE_INT_MAX_HWIS): New.
>         (class fixed_wide_int_storage): Use it.
>         (trailing_wide_ints <N>::set_precision): Use it.
>         (trailing_wide_ints <N>::extra_size): Use it.
> ---
>  gcc/wide-int.h | 12 +++++++-----
>  1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/gcc/wide-int.h b/gcc/wide-int.h
> index a450a744c9f..6be343c0eb5 100644
> --- a/gcc/wide-int.h
> +++ b/gcc/wide-int.h
> @@ -264,6 +264,10 @@ along with GCC; see the file COPYING3.  If not see
>  /* The number of HWIs needed to store an offset_int.  */
>  #define OFFSET_INT_ELTS (ADDR_MAX_PRECISION / HOST_BITS_PER_WIDE_INT)
>
> +/* The max number of HWIs needed to store a wide_int of PRECISION.  */
> +#define WIDE_INT_MAX_HWIS(PRECISION) \
> +  ((PRECISION + HOST_BITS_PER_WIDE_INT - 1) / HOST_BITS_PER_WIDE_INT)

Does it make sense to use an constexpr inline function instead of a
define here since GCC is written in C++11 after all?
That is:
constexpr inline unsigned WIDE_INT_MAX_HWIS(unsigned precision)
{
  return ((precision + HOST_BITS_PER_WIDE_INT - 1) / HOST_BITS_PER_WIDE_INT);
}

Thanks,
Andrew Pinski

> +
>  /* The type of result produced by a binary operation on types T1 and T2.
>     Defined purely for brevity.  */
>  #define WI_BINARY_RESULT(T1, T2) \
> @@ -1214,7 +1218,7 @@ template <int N>
>  class GTY(()) fixed_wide_int_storage
>  {
>  private:
> -  HOST_WIDE_INT val[(N + HOST_BITS_PER_WIDE_INT + 1) / HOST_BITS_PER_WIDE_INT];
> +  HOST_WIDE_INT val[WIDE_INT_MAX_HWIS (N)];
>    unsigned int len;
>
>  public:
> @@ -1475,8 +1479,7 @@ trailing_wide_ints <N>::set_precision (unsigned int precision,
>    gcc_checking_assert (num_elements <= N);
>    m_num_elements = num_elements;
>    m_precision = precision;
> -  m_max_len = ((precision + HOST_BITS_PER_WIDE_INT - 1)
> -              / HOST_BITS_PER_WIDE_INT);
> +  m_max_len = WIDE_INT_MAX_HWIS (precision);
>  }
>
>  /* Return a reference to element INDEX.  */
> @@ -1505,8 +1508,7 @@ inline size_t
>  trailing_wide_ints <N>::extra_size (unsigned int precision,
>                                     unsigned int num_elements)
>  {
> -  unsigned int max_len = ((precision + HOST_BITS_PER_WIDE_INT - 1)
> -                         / HOST_BITS_PER_WIDE_INT);
> +  unsigned int max_len = WIDE_INT_MAX_HWIS (precision);
>    gcc_checking_assert (num_elements <= N);
>    return (num_elements * max_len - 1) * sizeof (HOST_WIDE_INT);
>  }
> --
> 2.39.2
>

  reply	other threads:[~2023-04-17 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 18:39 Aldy Hernandez
2023-04-17 18:47 ` Andrew Pinski [this message]
2023-04-17 18:50   ` Aldy Hernandez
2023-04-18  6:18     ` Richard Biener

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='CA+=Sn1=cBQ3V-SsXwcLVMoSL89-uGY0p8tGGOQdGUgJ_xeyxpA@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=aldyh@redhat.com \
    --cc=amacleod@redhat.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).