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/103977] [12 Regression] ice in try_vectorize_loop_1 since r12-6420-gd3ff7420e941931d32ce2e332e7968fe67ba20af
Date: Tue, 11 Jan 2022 12:59:30 +0000	[thread overview]
Message-ID: <bug-103977-4-9LlzU3rzzF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103977-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
  /* For epilogues start the analysis from the first mode.  The motivation
     behind starting from the beginning comes from cases where the VECTOR_MODES
     array may contain length-agnostic and length-specific modes.  Their
     ordering is not guaranteed, so we could end up picking a mode for the main
     loop that is after the epilogue's optimal mode.  */
  mode_i = 1;

that's only valid if vector_modes.length () > 1 but for the testcase it only
contains the artificial VOIDmode aka autodetect mode.  I wonder why
we don't start from 0?

  parent reply	other threads:[~2022-01-11 12:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 12:10 [Bug c/103977] New: ice in try_vectorize_loop_1 dcb314 at hotmail dot com
2022-01-11 12:17 ` [Bug tree-optimization/103977] " jakub at gcc dot gnu.org
2022-01-11 12:43 ` [Bug tree-optimization/103977] [12 Regression] ice in try_vectorize_loop_1 since r12-6420-gd3ff7420e941931d32ce2e332e7968fe67ba20af dcb314 at hotmail dot com
2022-01-11 12:59 ` rguenth at gcc dot gnu.org [this message]
2022-01-11 23:30 ` law at gcc dot gnu.org
2022-01-12 10:20 ` avieira at gcc dot gnu.org
2022-01-12 16:04 ` law at gcc dot gnu.org
2022-01-12 16:10 ` avieira at gcc dot gnu.org
2022-01-12 16:17 ` avieira at gcc dot gnu.org
2022-01-13  7:13 ` 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-103977-4-9LlzU3rzzF@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).