public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97255] [8/9/10 Regression] Vectorizer gives a boolean a value of 255
Date: Thu, 01 Oct 2020 10:36:31 +0000	[thread overview]
Message-ID: <bug-97255-4-MwnzW2ehTD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97255-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97255

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[8/9/10/11 Regression]      |[8/9/10 Regression]
                   |Vectorizer gives a boolean  |Vectorizer gives a boolean
                   |a value of 255              |a value of 255
      Known to work|                            |11.0
           Priority|P3                          |P2

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
commit 36e691d3a62145fda1f4a1b3143d215cc113c10a (origin/master, origin/HEAD)
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Oct 1 09:29:32 2020 +0200

    tree-optimization/97255 - missing vector bool pattern of SRAed bool

    SRA tends to use VIEW_CONVERT_EXPR when replacing bool fields with
    unsigned char fields.  Those are not handled in vector bool pattern
    detection causing vector true values to leak.  The following fixes
    this by turning those into b ? 1 : 0 as well.

    2020-10-01  Richard Biener  <rguenther@suse.de>

            * tree-vect-patterns.c (vect_recog_bool_pattern): Also handle
            VIEW_CONVERT_EXPR.

            * g++.dg/vect/pr97255.cc: New testcase.

  parent reply	other threads:[~2020-10-01 10:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 12:45 [Bug c++/97255] New: " iwans at xilinx dot com
2020-09-30 14:12 ` [Bug c++/97255] [8/9/10/11 Regression] " marxin at gcc dot gnu.org
2020-09-30 15:01 ` [Bug tree-optimization/97255] " rguenth at gcc dot gnu.org
2020-10-01  7:24 ` rguenth at gcc dot gnu.org
2020-10-01 10:36 ` rguenth at gcc dot gnu.org [this message]
2020-10-12  8:28 ` [Bug tree-optimization/97255] [8/9/10 " cvs-commit at gcc dot gnu.org
2020-12-02 12:21 ` [Bug tree-optimization/97255] [8/9 " cvs-commit at gcc dot gnu.org
2021-03-17 11:14 ` [Bug tree-optimization/97255] [8 " cvs-commit at gcc dot gnu.org
2021-03-17 11:16 ` rguenth at gcc dot gnu.org

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=bug-97255-4-MwnzW2ehTD@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).