public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103489] [11 Regression] ICE with -O3 in operator[], at vec.h:889 since r12-5394-g0fc859f5efcb4624
Date: Fri, 28 Jan 2022 14:16:31 +0000	[thread overview]
Message-ID: <bug-103489-4-DWktqHcNuI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103489-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:2c7d8ca8317981c2eb21eb1e85e0f55d3f71aff1

commit r11-9523-g2c7d8ca8317981c2eb21eb1e85e0f55d3f71aff1
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Nov 30 14:08:19 2021 +0100

    tree-optimization/103489 - fix ICE when bool pattern recog fails

    bool pattern recog currently does not handle cycles correctly
    and when it fails we can ICE later vectorizing PHIs with
    mismatched bool and non-bool vector types.  The following avoids
    blindly trusting bool pattern recog here and verifies things
    more thoroughly in vectorizable_phi.  A bool pattern recog fix
    is for GCC 13.

    2021-11-30  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/103489
            * tree-vect-loop.c (vectorizable_phi): Verify argument
            vector type compatibility to mitigate bool pattern recog
            bug.

            * gcc.dg/torture/pr103489.c: New testcase.

    (cherry picked from commit 0194d92c35ca8b3aa850b805d9becb4491cf6bec)

  parent reply	other threads:[~2022-01-28 14:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30  9:20 [Bug tree-optimization/103489] New: ICE with -O3 in operator[], at vec.h:889 vsevolod.livinskij at frtk dot ru
2021-11-30 12:24 ` [Bug tree-optimization/103489] [12 Regression] " rguenth at gcc dot gnu.org
2021-11-30 13:06 ` rguenth at gcc dot gnu.org
2021-11-30 13:12 ` [Bug tree-optimization/103489] [11/12 " rguenth at gcc dot gnu.org
2021-11-30 13:15 ` rguenth at gcc dot gnu.org
2021-11-30 14:01 ` cvs-commit at gcc dot gnu.org
2021-11-30 14:01 ` [Bug tree-optimization/103489] [11 " rguenth at gcc dot gnu.org
2021-11-30 14:13 ` [Bug tree-optimization/103489] [11 Regression] ICE with -O3 in operator[], at vec.h:889 since r12-5394-g0fc859f5efcb4624 marxin at gcc dot gnu.org
2021-11-30 14:23 ` rguenth at gcc dot gnu.org
2022-01-28 14:16 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-28 14: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-103489-4-DWktqHcNuI@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).