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/111614] New: [14 Regression] ICE at -O2: verify_gimple failed since r14-2282-gf703d2fd3f0 Date: Wed, 27 Sep 2023 13:39:51 +0000 [thread overview] Message-ID: <bug-111614-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111614 Bug ID: 111614 Summary: [14 Regression] ICE at -O2: verify_gimple failed since r14-2282-gf703d2fd3f0 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: rguenth at gcc dot gnu.org Target Milestone: --- gcc at -O2 crashes. Bisected to r14-2282-gf703d2fd3f0 Compiler explorer: https://godbolt.org/z/xG5Tosvnc $ cat a.c int a, b, c, d, e; static void f() { int *g = &b; b = 1; for (; b >= 0; b--) { c = 0; for (; c <= 1; c++) e = 0; for (; e <= 1; e++) { int h, i = h = 13; for (; h; h--) i = i << a; d &= i + c + 9 + *g; } } } int main() { f(); for (;;) ; } $ $ gcc -O3 a.c a.c: In function ‘main’: a.c:17:5: error: type mismatch in binary expression 17 | int main() { | ^~~~ vector(2) int vector(2) int vector(2) unsigned int _15 = vect__15.28_19 & _11; during GIMPLE pass: reassoc a.c:17:5: internal compiler error: verify_gimple failed 0x7f6a86416082 __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-09-27 13:39 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-27 13:39 shaohua.li at inf dot ethz.ch [this message] 2023-09-27 18:36 ` [Bug tree-optimization/111614] " pinskia at gcc dot gnu.org 2023-09-27 18:45 ` pinskia at gcc dot gnu.org 2023-09-28 7:42 ` rguenth at gcc dot gnu.org 2023-09-28 9:25 ` cvs-commit at gcc dot gnu.org 2023-09-28 9:26 ` [Bug tree-optimization/111614] [11/12/13 " rguenth at gcc dot gnu.org 2023-11-10 14:24 ` cvs-commit at gcc dot gnu.org 2023-11-27 13:09 ` [Bug tree-optimization/111614] [11/12 " cvs-commit at gcc dot gnu.org 2023-12-15 12:18 ` [Bug tree-optimization/111614] [11 " cvs-commit at gcc dot gnu.org 2023-12-15 12:23 ` rguenth at gcc dot gnu.org 2023-12-15 12:23 ` 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-111614-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).