public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113205] [14 Regression] internal compiler error: in backward_pass, at tree-vect-slp.cc:5346 since r14-3220 Date: Mon, 08 Jan 2024 17:17:47 +0000 [thread overview] Message-ID: <bug-113205-4-AqcQlwzc1f@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113205-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113205 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Keywords|needs-bisection, | |needs-reduction | Summary|[14 Regression] internal |[14 Regression] internal |compiler error: in |compiler error: in |backward_pass, at |backward_pass, at |tree-vect-slp.cc:5346 |tree-vect-slp.cc:5346 since | |r14-3220 Ever confirmed|0 |1 Last reconfirmed| |2024-01-08 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- char a; char *b, *c; int d, e, f, g, h; int *i; void foo (void) { unsigned p; d = i[0]; e = i[1]; f = i[2]; g = i[3]; p = d * b[0]; p += f * c[h]; p += e * b[h]; p += g * c[h]; a = (p + 8000) >> (__SIZEOF_INT__ * __CHAR_BIT__ / 2); } is reduced from mlt, ICEs at -O2 since r14-3220-gf049868d8db773da4be61d82025e97453d6e9f2b.
next prev parent reply other threads:[~2024-01-08 17:17 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-02 18:51 [Bug middle-end/113205] New: [14 Regression] internal compiler error: in backward_pass, at tree-vect-slp.cc:5346 doko at gcc dot gnu.org 2024-01-02 20:14 ` [Bug middle-end/113205] " doko at gcc dot gnu.org 2024-01-05 14:03 ` jakub at gcc dot gnu.org 2024-01-08 14:41 ` rguenth at gcc dot gnu.org 2024-01-08 17:17 ` jakub at gcc dot gnu.org [this message] 2024-01-08 17:18 ` [Bug middle-end/113205] [14 Regression] internal compiler error: in backward_pass, at tree-vect-slp.cc:5346 since r14-3220 jakub at gcc dot gnu.org 2024-01-10 8:12 ` rguenth at gcc dot gnu.org 2024-02-05 23:59 ` sergio at serjux dot com 2024-02-07 22:16 ` sergio at serjux dot com 2024-02-07 22:19 ` jakub at gcc dot gnu.org 2024-02-07 22:19 ` pinskia at gcc dot gnu.org 2024-02-09 1:18 ` sergio at serjux dot com 2024-02-09 7:24 ` rguenth at gcc dot gnu.org 2024-02-15 14:15 ` jakub at gcc dot gnu.org 2024-02-23 14:47 ` rsandifo at gcc dot gnu.org 2024-02-23 14:48 ` rsandifo at gcc dot gnu.org 2024-02-24 11:58 ` cvs-commit at gcc dot gnu.org 2024-02-24 11:59 ` rsandifo 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-113205-4-AqcQlwzc1f@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).