public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103523] [11/12 Regression] SVE float auto-vect float format expand failure exposed by r11-7861-ge4180ab2f
Date: Mon, 06 Dec 2021 12:10:21 +0000	[thread overview]
Message-ID: <bug-103523-4-Dt6dADVyXH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103523-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Looks like the ICE is cause by a bug in `vectorizable_induction` not checking
for MULT_EXPR and PLUS_EXPR for the given type before it tries to emit them.

This then leads to veclower trying to lower the operation since it's not
supported and then this ICEs since veclower can only handle fixed-size vectors.

The reason we generate this in the first place is due to the epilogue mask.

The main loop is vectorized using VNx4SF and we generate an epilogue for
VNx2SF.

  parent reply	other threads:[~2021-12-06 12:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 20:58 [Bug target/103523] New: [12 Regression] SVE float auto-vect float format expand failure tnfchris at gcc dot gnu.org
2021-12-01 21:19 ` [Bug target/103523] [11/12 " tnfchris at gcc dot gnu.org
2021-12-02  1:35 ` [Bug tree-optimization/103523] " pinskia at gcc dot gnu.org
2021-12-02  1:48 ` pinskia at gcc dot gnu.org
2021-12-02 10:57 ` rguenth at gcc dot gnu.org
2021-12-03  8:33 ` joelh at gcc dot gnu.org
2021-12-03  8:37 ` [Bug tree-optimization/103523] [11/12 Regression] SVE float auto-vect float format expand failure exposed by r11-7861-ge4180ab2f pinskia at gcc dot gnu.org
2021-12-06 12:10 ` tnfchris at gcc dot gnu.org [this message]
2021-12-10 10:28 ` [Bug tree-optimization/103523] [11/12 Regression] vectorizable_induction generating code for modes without checking support for them " cvs-commit at gcc dot gnu.org
2021-12-10 10:31 ` joelh at gcc dot gnu.org
2021-12-10 10:47 ` tnfchris at gcc dot gnu.org
2021-12-13 14:21 ` [Bug tree-optimization/103523] [11 " cvs-commit at gcc dot gnu.org
2021-12-15  9:28 ` joelh 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-103523-4-Dt6dADVyXH@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).