public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109392] [12/13 Regression] ICE in tree_vec_extract, at tree-vect-generic.cc:177
Date: Tue, 04 Apr 2023 00:45:40 +0000 [thread overview]
Message-ID: <bug-109392-4-QScAUVW1yI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109392-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109392
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-04-04
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.
Most likely caused by r12-117-gb972e036f40c .
I think the assert happens because the argument t is abnormal SSA_NAME and
resimplify/maybe_push_res_to_seq decides it can't do anything on it so returns
null.
next prev parent reply other threads:[~2023-04-04 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 16:50 [Bug c/109392] New: " gscfq@t-online.de
2023-04-03 18:08 ` [Bug tree-optimization/109392] " pinskia at gcc dot gnu.org
2023-04-04 0:45 ` pinskia at gcc dot gnu.org [this message]
2023-04-04 0:47 ` pinskia at gcc dot gnu.org
2023-04-04 8:14 ` [Bug tree-optimization/109392] [12/13 Regression] ICE in tree_vec_extract, at tree-vect-generic.cc:177 since r12-117-gb972e036f40c marxin at gcc dot gnu.org
2023-04-04 12:46 ` jakub at gcc dot gnu.org
2023-04-08 18:24 ` cvs-commit at gcc dot gnu.org
2023-04-11 8:17 ` [Bug tree-optimization/109392] [12 " rguenth at gcc dot gnu.org
2023-04-27 13:19 ` cvs-commit at gcc dot gnu.org
2023-04-27 13:20 ` 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-109392-4-QScAUVW1yI@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).