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/98928] [11 regression] ICE when build 638.imagick_s since r11-5969-g3ed472af6bc9f83b
Date: Wed, 03 Feb 2021 08:09:30 +0000	[thread overview]
Message-ID: <bug-98928-4-fwH6NGyETR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98928-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>:

https://gcc.gnu.org/g:5e606ed90a1bed878071b6b5a3ef9b97b3d99838

commit r11-7049-g5e606ed90a1bed878071b6b5a3ef9b97b3d99838
Author: Tamar Christina <tamar.christina@arm.com>
Date:   Wed Feb 3 08:06:11 2021 +0000

    slp: Split out patterns away from using SLP_ONLY into their own flag

    Previously the SLP pattern matcher was using STMT_VINFO_SLP_VECT_ONLY as a
way
    to dissolve the SLP only patterns during SLP cancellation.  However it
seems
    like the semantics for STMT_VINFO_SLP_VECT_ONLY are slightly different than
what
    I expected.

    Namely that the non-SLP path can still use a statement marked
    STMT_VINFO_SLP_VECT_ONLY.  One such example is masked loads which are used
both
    in the SLP and non-SLP path.

    To fix this I now introduce a new flag STMT_VINFO_SLP_VECT_ONLY_PATTERN
which is
    used only by the pattern matcher.

    gcc/ChangeLog:

            PR tree-optimization/98928
            * tree-vect-loop.c (vect_analyze_loop_2): Change
            STMT_VINFO_SLP_VECT_ONLY to STMT_VINFO_SLP_VECT_ONLY_PATTERN.
            * tree-vect-slp-patterns.c (complex_pattern::build): Likewise.
            * tree-vectorizer.h (STMT_VINFO_SLP_VECT_ONLY_PATTERN): New.
            (class _stmt_vec_info): Add slp_vect_pattern_only_p.

    gcc/testsuite/ChangeLog:

            PR tree-optimization/98928
            * gcc.target/i386/pr98928.c: New test.

  parent reply	other threads:[~2021-02-03  8:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  8:03 [Bug tree-optimization/98928] New: [11 regression] ICE when build 638.imagick_s crazylht at gmail dot com
2021-02-02  8:24 ` [Bug tree-optimization/98928] " rguenth at gcc dot gnu.org
2021-02-02  8:58 ` marxin at gcc dot gnu.org
2021-02-02 10:33 ` marxin at gcc dot gnu.org
2021-02-02 10:33 ` [Bug tree-optimization/98928] [11 regression] ICE when build 638.imagick_s since r11-5969-g3ed472af6bc9f83b marxin at gcc dot gnu.org
2021-02-02 12:43 ` tnfchris at gcc dot gnu.org
2021-02-02 14:58 ` tnfchris at gcc dot gnu.org
2021-02-03  8:09 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-03  8:10 ` tnfchris 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-98928-4-fwH6NGyETR@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).