public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Ilya Enkovich <enkovich.gnu@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Use signed boolean type for boolean vectors
Date: Wed, 28 Oct 2015 15:24:00 -0000	[thread overview]
Message-ID: <CAFiYyc1B2Jgt_qHSvnSviuhzn1CVoAqRqoJNMOYu7F=ZQa5xNg@mail.gmail.com> (raw)
In-Reply-To: <20151028131339.GC20857@msticlxl57.ims.intel.com>

On Wed, Oct 28, 2015 at 2:13 PM, Ilya Enkovich <enkovich.gnu@gmail.com> wrote:
> Hi,
>
> Testing boolean vector conversions I found several runtime regressions
> and investigation showed it's due to incorrect conversion caused by
> unsigned boolean type.  When boolean vector is represented as an
> integer vector on target it's a signed integer actually.  Unsigned
> boolean type was chosen due to possible single bit values, but for
> multiple bit values it causes wrong casting.  The easiest way to fix
> it is to use signed boolean value.  The following patch does this and
> fixes my problems with conversion.  Bootstrapped and tested on
> x86_64-unknown-linux-gnu.  Is it OK?

Hmm.  Actually formally the "boolean" vectors were always 0 or -1
(all bits set).  That is also true for a signed boolean with precision 1
but with higher precision what makes sure to sign-extend 'true'?

So it's far from an obvious change, esp as you don't change the
precision == 1 case.  [I still think we should have precision == 1
for all boolean types]

Richard.

> Thanks,
> Ilya
> --
> gcc/
>
> 2015-10-28  Ilya Enkovich  <enkovich.gnu@gmail.com>
>
>         * optabs.c (expand_vec_cond_expr): Always get sign from type.
>         * tree.c (wide_int_to_tree): Support negative values for boolean.
>         (build_nonstandard_boolean_type): Use signed type for booleans
>         with precision greater than 1.
>
>
> diff --git a/gcc/optabs.c b/gcc/optabs.c
> index e1ac0b8..37a67f1 100644
> --- a/gcc/optabs.c
> +++ b/gcc/optabs.c
> @@ -5373,7 +5373,6 @@ expand_vec_cond_expr (tree vec_cond_type, tree op0, tree op1, tree op2,
>        op0a = TREE_OPERAND (op0, 0);
>        op0b = TREE_OPERAND (op0, 1);
>        tcode = TREE_CODE (op0);
> -      unsignedp = TYPE_UNSIGNED (TREE_TYPE (op0a));
>      }
>    else
>      {
> @@ -5382,9 +5381,9 @@ expand_vec_cond_expr (tree vec_cond_type, tree op0, tree op1, tree op2,
>        op0a = op0;
>        op0b = build_zero_cst (TREE_TYPE (op0));
>        tcode = LT_EXPR;
> -      unsignedp = false;
>      }
>    cmp_op_mode = TYPE_MODE (TREE_TYPE (op0a));
> +  unsignedp = TYPE_UNSIGNED (TREE_TYPE (op0a));
>
>
>    gcc_assert (GET_MODE_SIZE (mode) == GET_MODE_SIZE (cmp_op_mode)
> diff --git a/gcc/tree.c b/gcc/tree.c
> index e77d4b8..712390f 100644
> --- a/gcc/tree.c
> +++ b/gcc/tree.c
> @@ -1451,7 +1451,7 @@ wide_int_to_tree (tree type, const wide_int_ref &pcst)
>         case BOOLEAN_TYPE:
>           /* Cache false or true.  */
>           limit = 2;
> -         if (hwi < 2)
> +         if (IN_RANGE (hwi, 0, 1))
>             ix = hwi;
>           break;
>
> @@ -8076,7 +8076,10 @@ build_nonstandard_boolean_type (unsigned HOST_WIDE_INT precision)
>
>    type = make_node (BOOLEAN_TYPE);
>    TYPE_PRECISION (type) = precision;
> -  fixup_unsigned_type (type);
> +  if (precision > 1)
> +    fixup_signed_type (type);
> +  else
> +    fixup_unsigned_type (type);
>
>    if (precision <= MAX_INT_CACHED_PREC)
>      nonstandard_boolean_type_cache[precision] = type;

  reply	other threads:[~2015-10-28 15:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 13:33 Ilya Enkovich
2015-10-28 15:24 ` Richard Biener [this message]
2015-10-28 15:31   ` Ilya Enkovich
2015-11-03 13:42     ` Richard Biener
2015-11-09 14:04       ` Ilya Enkovich
2015-11-09 14:27         ` 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='CAFiYyc1B2Jgt_qHSvnSviuhzn1CVoAqRqoJNMOYu7F=ZQa5xNg@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=enkovich.gnu@gmail.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).