public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107300] New: ICE: verify_ssa failed (error: virtual definition of statement not up to date)
Date: Tue, 18 Oct 2022 03:33:26 +0000 [thread overview]
Message-ID: <bug-107300-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107300
Bug ID: 107300
Summary: ICE: verify_ssa failed (error: virtual definition of
statement not up to date)
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gcc 13.0.0 20221016 snapshot (g:6366e3e8847af98d4728d55951534769d034d02a) ICEs
when compiling the following testcase, reduced from
gcc/testsuite/gcc.c-torture/execute/pr81281.c, w/ -O2 -fipa-cp-clone
-funreachable-traps -fno-inline:
void
bar (int x, int y)
{
if (x)
__builtin_unreachable ();
if (y)
__builtin_abort ();
}
void
foo (void)
{
bar (0, 0);
}
% gcc-13 -O2 -fipa-cp-clone -funreachable-traps -fno-inline -c bppprfmm.c
bppprfmm.c: In function 'bar.constprop':
bppprfmm.c:2:1: error: virtual definition of statement not up to date
2 | bar (int x, int y)
| ^~~
__builtin_trap ();
during GIMPLE pass: fixup_cfg
bppprfmm.c:2:1: internal compiler error: verify_ssa failed
0x1155fd5 verify_ssa(bool, bool)
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221016/work/gcc-13-20221016/gcc/tree-ssa.cc:1211
0xe0737d execute_function_todo
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221016/work/gcc-13-20221016/gcc/passes.cc:2098
0xe077ae execute_todo
/var/tmp/portage/sys-devel/gcc-13.0.0_p20221016/work/gcc-13-20221016/gcc/passes.cc:2145
next reply other threads:[~2022-10-18 3:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 3:33 asolokha at gmx dot com [this message]
2022-10-18 7:32 ` [Bug ipa/107300] [13 Regression] " rguenth at gcc dot gnu.org
2022-10-18 7:54 ` marxin at gcc dot gnu.org
2022-10-18 7:55 ` rguenth at gcc dot gnu.org
2022-10-19 17:34 ` pinskia at gcc dot gnu.org
2022-11-30 17:10 ` jakub at gcc dot gnu.org
2022-12-01 15:11 ` marxin at gcc dot gnu.org
2022-12-01 15:27 ` jakub at gcc dot gnu.org
2022-12-20 14:36 ` rguenth at gcc dot gnu.org
2023-02-02 9:55 ` cvs-commit at gcc dot gnu.org
2023-02-02 12:57 ` 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-107300-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).