public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108655] New: ICE in execute_todo, at passes.cc:2134 since r13-1204-gd68d366425369649
Date: Fri, 03 Feb 2023 09:13:14 +0000 [thread overview]
Message-ID: <bug-108655-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108655
Bug ID: 108655
Summary: ICE in execute_todo, at passes.cc:2134 since
r13-1204-gd68d366425369649
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: jason at redhat dot com
Target Milestone: ---
The following ICEs:
$ int
test_collapse() {
int i;
for (; i;)
;
for (; i < 6;)
for (int j = 0; j < 6; ++j)
i += j;
}
$ gcc simd.c -c -O1 -funreachable-traps
during GIMPLE pass: ivcanon
simd.c: In function ‘test_collapse’:
simd.c:2:1: internal compiler error: in execute_todo, at passes.cc:2140
2 | test_collapse() {
| ^~~~~~~~~~~~~
0x721e5f execute_todo
/home/marxin/Programming/gcc/gcc/passes.cc:2140
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2023-02-03 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 9:13 marxin at gcc dot gnu.org [this message]
2023-02-03 9:14 ` [Bug c++/108655] " marxin at gcc dot gnu.org
2023-02-03 10:45 ` [Bug tree-optimization/108655] [13 Regression] " jakub at gcc dot gnu.org
2023-02-03 10:56 ` jakub at gcc dot gnu.org
2023-02-06 8:06 ` cvs-commit at gcc dot gnu.org
2023-02-06 8:07 ` jakub 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-108655-4@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).