public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/105163] New: ICE: SSA corruption Date: Tue, 05 Apr 2022 16:16:33 +0000 [thread overview] Message-ID: <bug-105163-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105163 Bug ID: 105163 Summary: ICE: SSA corruption Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Affects versions down to at least r5, at -O1+ : (follow-up of pr79411.c) $ cat z1.c typedef struct __jmp_buf_tag { char buf[1024]; } jmp_buf[1]; extern int setjmp (jmp_buf); extern int bar (unsigned int *); extern jmp_buf *baz (void); struct C { int c1; }; void foo (struct C *x, int *z, int e) { unsigned int d = 0; long f; setjmp (*baz()); f = 1 + ~d; d = 8; if ((!0) && !e && bar(z)) *z = 1 + f; } $ gcc-12-20220403 -c z1.c -O2 Unable to coalesce ssa_names 5 and 17 which are marked as MUST COALESCE. d_5(ab) and d_17(ab) during RTL pass: expand z1.c: In function 'foo': z1.c:6:6: internal compiler error: SSA corruption 6 | void foo (struct C *x, int *z, int e) | ^~~ 0xd18bc8 fail_abnormal_edge_coalesce ../../gcc/tree-ssa-coalesce.cc:1003 0xd18bc8 coalesce_partitions ../../gcc/tree-ssa-coalesce.cc:1425 0xd18bc8 coalesce_ssa_name(_var_map*) ../../gcc/tree-ssa-coalesce.cc:1755 0xcc26a0 remove_ssa_form ../../gcc/tree-outof-ssa.cc:1065 0xcc26a0 rewrite_out_of_ssa(ssaexpand*) ../../gcc/tree-outof-ssa.cc:1323 0x7cfa73 execute ../../gcc/cfgexpand.cc:6585
next reply other threads:[~2022-04-05 16:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-05 16:16 gscfq@t-online.de [this message] 2022-04-05 16:17 ` [Bug c/105163] " gscfq@t-online.de 2022-04-05 16:59 ` [Bug tree-optimization/105163] " jakub at gcc dot gnu.org 2022-04-05 17:00 ` [Bug tree-optimization/105163] [9/10/11/12 Regression] ICE: SSA corruption since r0-122928 jakub at gcc dot gnu.org 2022-04-06 7:15 ` rguenth at gcc dot gnu.org 2022-04-06 8:33 ` cvs-commit at gcc dot gnu.org 2022-05-19 14:03 ` [Bug tree-optimization/105163] [9/10/11 " cvs-commit at gcc dot gnu.org 2022-05-27 9:47 ` [Bug tree-optimization/105163] [10 " rguenth at gcc dot gnu.org 2022-05-27 13:15 ` cvs-commit at gcc dot gnu.org 2022-05-27 13:18 ` 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-105163-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).