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/111866] [14 regression] ICE when compiling gcc.target/powerpc/p9-vec-length-full-7.c Date: Thu, 19 Oct 2023 11:07:10 +0000 [thread overview] Message-ID: <bug-111866-4-4rdILboB4z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111866-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111866 --- Comment #3 from Tamar Christina <tnfchris at gcc dot gnu.org> --- ok, so the crash looks like it's due to rgroups_control being empty during prologue peeling. It looks like the loop isn't masked so LOOP_VINFO_LENS (loop_vinfo) is being used in this case, but (!rgc->controls.is_empty ()) fails. As far as I can tell these are only filled in by vect_get_loop_len. It looks like after the refactoring vect_get_loop_len is not being called. It was expected to be called from vectorizable_store. Debugging why it doesn't get there.
next prev parent reply other threads:[~2023-10-19 11:07 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-18 15:49 [Bug middle-end/111866] New: [14 regression] ICE when compiling seurer at gcc dot gnu.org 2023-10-18 16:06 ` [Bug middle-end/111866] [14 regression] ICE when compiling gcc.target/powerpc/p9-vec-length-full-7.c tnfchris at gcc dot gnu.org 2023-10-18 16:07 ` [Bug tree-optimization/111866] " tnfchris at gcc dot gnu.org 2023-10-18 18:57 ` pinskia at gcc dot gnu.org 2023-10-19 11:07 ` tnfchris at gcc dot gnu.org [this message] 2023-10-20 10:58 ` tnfchris at gcc dot gnu.org 2023-10-20 14:00 ` cvs-commit at gcc dot gnu.org 2023-10-20 14:02 ` 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-111866-4-4rdILboB4z@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: linkBe 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).