From: Richard Sandiford <richard.sandiford@arm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] wide-int: Fix up wi::shifted_mask [PR106144]
Date: Fri, 01 Jul 2022 10:11:02 +0100 [thread overview]
Message-ID: <mpto7y98aft.fsf@arm.com> (raw)
In-Reply-To: <Yr6hObntpK6Fo9bj@tucnak> (Jakub Jelinek's message of "Fri, 1 Jul 2022 09:24:41 +0200")
Jakub Jelinek <jakub@redhat.com> writes:
> Hi!
>
> As the following self-test testcase shows, wi::shifted_mask sometimes
> doesn't create canonicalized wide_ints, which then fail to compare equal
> to canonicalized wide_ints with the same value.
> In particular, wi::mask (128, false, 128) gives { -1 } with len 1 and prec 128,
> while wi::shifted_mask (0, 128, false, 128) gives { -1, -1 } with len 2
> and prec 128.
> The problem is that the code is written with the assumption that there are
> 3 bit blocks (or 2 if start is 0), but doesn't consider the possibility
> where there are 2 bit blocks (or 1 if start is 0) where the highest block
> isn't present. In that case, there is the optional block of negate ? 0 : -1
> elts, followed by just one elt (either one from the if (shift) or just
> negate ? -1 : 0) and the rest is implicit sign-extension.
> Only if end < prec there is 1 or more bits above it that have different bit
> value and so we need to emit all the elts till end and then one more elt.
>
> if (end == prec) would work too, because we have:
> if (width > prec - start)
> width = prec - start;
> unsigned int end = start + width;
> so end is guaranteed to be end <= prec, dunno what is preferred.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
>
> 2022-07-01 Jakub Jelinek <jakub@redhat.com>
>
> PR middle-end/106144
> * wide-int.cc (wi::shifted_mask): If end >= prec, return right after
> emitting element for shift or if shift is 0 first element after start.
> (wide_int_cc_tests): Add tests for equivalency of wi::mask and
> wi::shifted_mask with 0 start.
OK, thanks, but could you also remove the "end < prec" condition from:
else if (end < prec)
val[i++] = negate ? -1 : 0;
Richard
> --- gcc/wide-int.cc.jj 2022-01-11 23:11:23.592273263 +0100
> +++ gcc/wide-int.cc 2022-06-30 20:41:25.506292687 +0200
> @@ -842,6 +842,13 @@ wi::shifted_mask (HOST_WIDE_INT *val, un
> val[i++] = negate ? block : ~block;
> }
>
> + if (end >= prec)
> + {
> + if (!shift)
> + val[i++] = negate ? 0 : -1;
> + return i;
> + }
> +
> while (i < end / HOST_BITS_PER_WIDE_INT)
> /* 1111111 */
> val[i++] = negate ? 0 : -1;
> @@ -2583,6 +2590,10 @@ wide_int_cc_tests ()
> run_all_wide_int_tests <widest_int> ();
> test_overflow ();
> test_round_for_mask ();
> + ASSERT_EQ (wi::mask (128, false, 128),
> + wi::shifted_mask (0, 128, false, 128));
> + ASSERT_EQ (wi::mask (128, true, 128),
> + wi::shifted_mask (0, 128, true, 128));
> }
>
> } // namespace selftest
>
> Jakub
prev parent reply other threads:[~2022-07-01 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 7:24 Jakub Jelinek
2022-07-01 9:11 ` Richard Sandiford [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=mpto7y98aft.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).