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/110221] New: With AVX512 fully masking gfortran.dg/pr68146.f ICEs
Date: Mon, 12 Jun 2023 12:45:16 +0000	[thread overview]
Message-ID: <bug-110221-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110221
           Summary: With AVX512 fully masking gfortran.dg/pr68146.f ICEs
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org
  Target Milestone: ---

The testcase ICEs with -march=znver4 --param vect-partial-vector-usage=2
because
invariant .COND_* functions with conditional masks that end up being invariant
get scheduled ahead of the loop by SLP.

This is similar to PR108979 but complicated by the conditional mask being
originally computed inside of the loop (so not vect_external_def).

             reply	other threads:[~2023-06-12 12:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 12:45 rguenth at gcc dot gnu.org [this message]
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

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@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).