public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114259] New: [14 Regression] ICE during GIMPLE pass: slp: internal compiler error: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:85
Date: Wed, 06 Mar 2024 18:14:34 +0000 [thread overview]
Message-ID: <bug-114259-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114259
Bug ID: 114259
Summary: [14 Regression] ICE during GIMPLE pass: slp: internal
compiler error: tree check: expected class 'type',
have 'exceptional' (error_mark) in
useless_type_conversion_p, at gimple-expr.cc:85
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: patrick at rivosinc dot com
Target Milestone: ---
Created attachment 57637
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57637&action=edit
-freport-bug output
Testcase:
Testcase:
long h;
int i;
char j;
short volatile k;
void l() {
i = h = 0;
for (; h < 7; h = h += 1)
i ^= (0 != k) + (long)j;
}
Backtrace:
> /scratch/tc-testing/tc-mar-5/build-rv64gcv/bin/riscv64-unknown-linux-gnu-gcc -march=rv64gcv -O3 red.c -o red.out
during GIMPLE pass: slp
./red.c: In function 'l':
./red.c:6:6: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.cc:85
6 | void l() {
| ^
0xb0f001 tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)
../../../gcc/gcc/tree.cc:9005
0xa38bd5 tree_class_check(tree_node*, tree_code_class, char const*, int, char
const*)
../../../gcc/gcc/tree.h:3767
0xa38bd5 useless_type_conversion_p(tree_node*, tree_node*)
../../../gcc/gcc/gimple-expr.cc:85
0x1365242 verify_gimple_assign_binary
../../../gcc/gcc/tree-cfg.cc:4305
0x13704ee verify_gimple_in_cfg(function*, bool, bool)
../../../gcc/gcc/tree-cfg.cc:5599
0x11f1b10 execute_function_todo
../../../gcc/gcc/passes.cc:2088
0x11f205b execute_todo
../../../gcc/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.
Godbolt: https://godbolt.org/z/s1M1WcGvc
Looks like a recent regression (within 2 days) since the fuzzer found ~10
instances of this failure last night.
Found via fuzzer.
next reply other threads:[~2024-03-06 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 18:14 patrick at rivosinc dot com [this message]
2024-03-06 18:21 ` [Bug tree-optimization/114259] " sjames at gcc dot gnu.org
2024-03-06 18:37 ` patrick at rivosinc dot com
2024-03-06 18:38 ` sjames 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-114259-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).