public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "shaohua.li at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112831] New: ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in type_has_mode_precision_p, at tree.h:6767 Date: Sun, 03 Dec 2023 14:38:15 +0000 [thread overview] Message-ID: <bug-112831-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112831 Bug ID: 112831 Summary: ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in type_has_mode_precision_p, at tree.h:6767 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: shaohua.li at inf dot ethz.ch CC: fweimer at redhat dot com Target Milestone: --- gcc at -Os crashes on the test case. Bisected to r14-6034-g4ee2aca7ca0 Compiler explorer: https://godbolt.org/z/6We5qxMbr % cat a.c int a, b; char c; int d() {} void e() { for (; c; c++) { b = 0; for (; b <= 7; b++) ; for (; (short)(d() + b) + a; a++) ; } } int main() {} % % gcc -Os a.c during GIMPLE pass: sccp a.c: In function ‘e’: a.c:4:6: internal compiler error: tree check: expected class ‘type’, have ‘exceptional’ (error_mark) in type_has_mode_precision_p, at tree.h:6767 4 | void e() { | ^ 0x7f47566c3082 __libc_start_main ../csu/libc-start.c:308 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-12-03 14:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-03 14:38 shaohua.li at inf dot ethz.ch [this message] 2023-12-03 17:15 ` [Bug tree-optimization/112831] " fw at gcc dot gnu.org 2023-12-03 17:15 ` fw at gcc dot gnu.org 2023-12-03 21:27 ` [Bug tree-optimization/112831] [14 Regression] " pinskia at gcc dot gnu.org 2023-12-03 21:29 ` pinskia at gcc dot gnu.org 2023-12-04 8:41 ` rguenth at gcc dot gnu.org 2023-12-04 9:44 ` rguenth 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-112831-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: 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).