public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mjires at suse dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112734] New: ICE verify_gimple failed since r14-3751-g8c984a1c3693df - BitInt
Date: Mon, 27 Nov 2023 19:52:34 +0000 [thread overview]
Message-ID: <bug-112734-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112734
Bug ID: 112734
Summary: ICE verify_gimple failed since
r14-3751-g8c984a1c3693df - BitInt
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: mjires at suse dot cz
CC: jakub at redhat dot com
Target Milestone: ---
Compiling reduced testcase gcc.dg/torture/bitint-3.c results in ICE.
$ cat bitint-3.c
_BitInt(128) out;
void main() {
_BitInt(8) q[1];
out -= 1;
}
$ gcc bitint-3.c -fnon-call-exceptions -ftrapv
bitint-3.c: In function ‘main’:
bitint-3.c:2:6: error: statement marked for throw in middle of block
2 | void main() {
| ^~~~
_7 = _8 + -1;
during GIMPLE pass: bitintlower0
bitint-3.c:2:6: internal compiler error: verify_gimple failed
0x105897d verify_gimple_in_cfg(function*, bool, bool)
/home/mjires/git/GCC/master/gcc/tree-cfg.cc:5662
0xee8ad4 execute_function_todo
/home/mjires/git/GCC/master/gcc/passes.cc:2088
0xee902e execute_todo
/home/mjires/git/GCC/master/gcc/passes.cc:2142
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.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/home/mjires/built/master/libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /home/mjires/git/GCC/master/configure
--prefix=/home/mjires/built/master --disable-bootstrap --enable-checking
--enable-languages=c,c++,fortran,lto
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20231127 (experimental) (GCC)
next reply other threads:[~2023-11-27 19:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 19:52 mjires at suse dot cz [this message]
2023-11-28 2:02 ` [Bug tree-optimization/112734] " pinskia at gcc dot gnu.org
2023-11-28 9:06 ` jakub at gcc dot gnu.org
2023-11-28 9:09 ` jakub at gcc dot gnu.org
2023-11-28 11:26 ` rguenth at gcc dot gnu.org
2023-11-28 11:39 ` jakub at gcc dot gnu.org
2023-11-29 23:23 ` [Bug tree-optimization/112734] [14 regression] " sjames at gcc dot gnu.org
2024-01-10 13:44 ` [Bug tree-optimization/112734] " rguenth at gcc dot gnu.org
2024-01-10 15:51 ` jakub at gcc dot gnu.org
2024-01-10 16:19 ` cvs-commit at gcc dot gnu.org
2024-01-10 16:24 ` jakub at gcc dot gnu.org
2024-01-20 17:25 ` pinskia 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-112734-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).