public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110443] [14 Regression] ICE on a52dec-0.7.4: GIMPLE pass: vect SIGSEGV in vect_get_gather_scatter_ops()
Date: Tue, 27 Jun 2023 22:52:30 +0000 [thread overview]
Message-ID: <bug-110443-4-Bik0YxHNt6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110443-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110443
--- Comment #3 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
(In reply to Sergei Trofimovich from comment #2)
> I wonder if it's a r14-2117-gdd86a5a69cbda4 "tree-optimization/96208 - SLP
> of non-grouped loads".
Reverting r14-2117-gdd86a5a69cbda4 fixes a52dec-0.7.4 for me.
next prev parent reply other threads:[~2023-06-27 22:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 19:46 [Bug middle-end/110443] New: [14 Regression] ICE on a52dec-0.7.4: slyfox at gcc dot gnu.org
2023-06-27 19:47 ` [Bug middle-end/110443] " pinskia at gcc dot gnu.org
2023-06-27 19:50 ` pinskia at gcc dot gnu.org
2023-06-27 22:20 ` [Bug middle-end/110443] [14 Regression] ICE on a52dec-0.7.4: GIMPLE pass: vect SIGSEGV in vect_get_gather_scatter_ops() slyfox at gcc dot gnu.org
2023-06-27 22:52 ` slyfox at gcc dot gnu.org [this message]
2023-06-28 7:56 ` rguenth at gcc dot gnu.org
2023-06-28 9:13 ` cvs-commit at gcc dot gnu.org
2023-06-28 9:13 ` rguenth at gcc dot gnu.org
2023-06-28 9:13 ` rguenth at gcc dot gnu.org
2023-06-28 13:55 ` slyfox at gcc dot gnu.org
2023-06-29 23:33 ` seurer at gcc dot gnu.org
2023-06-30 6:18 ` 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-110443-4-Bik0YxHNt6@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).