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/110221] With AVX512 fully masking gfortran.dg/pr68146.f ICEs
Date: Fri, 01 Mar 2024 13:40:58 +0000	[thread overview]
Message-ID: <bug-110221-4-6fMgbVYhu2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110221-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Andre Simoes Dias Vieira
<avieira@gcc.gnu.org>:

https://gcc.gnu.org/g:9d033155254ac6df5f47ab32896dbf336f991589

commit r12-10186-g9d033155254ac6df5f47ab32896dbf336f991589
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Nov 10 12:39:11 2023 +0100

    tree-optimization/110221 - SLP and loop mask/len

    The following fixes the issue that when SLP stmts are internal defs
    but appear invariant because they end up only using invariant defs
    then they get scheduled outside of the loop.  This nice optimization
    breaks down when loop masks or lens are applied since those are not
    explicitly tracked as dependences.  The following makes sure to never
    schedule internal defs outside of the vectorized loop when the
    loop uses masks/lens.

            PR tree-optimization/110221
            * tree-vect-slp.cc (vect_schedule_slp_node): When loop
            masking / len is applied make sure to not schedule
            intenal defs outside of the loop.

            * gfortran.dg/pr110221.f: New testcase.

    (cherry picked from commit 7c67939ec384425a3d7383dfb4fb39aa7e9ad20a)

      parent reply	other threads:[~2024-03-01 13:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 12:45 [Bug tree-optimization/110221] New: " rguenth at gcc dot gnu.org
2023-06-12 13:20 ` [Bug tree-optimization/110221] " rguenth at gcc dot gnu.org
2023-11-10 11:34 ` rguenth at gcc dot gnu.org
2023-11-10 13:17 ` cvs-commit at gcc dot gnu.org
2023-11-10 13:17 ` rguenth at gcc dot gnu.org
2024-01-17 11:46 ` saurabh.jha at arm dot com
2024-02-06 13:20 ` cvs-commit at gcc dot gnu.org
2024-03-01 13:40 ` cvs-commit at gcc dot gnu.org [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=bug-110221-4-6fMgbVYhu2@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).