public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106862] ice in compute_control_dep_chain, at gimple-predicate-analysis.cc:1105 Date: Tue, 06 Sep 2022 21:39:28 +0000 [thread overview] Message-ID: <bug-106862-4-Xlx7qhw1zI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106862-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106862 --- Comment #2 from David Binderman <dcb314 at hotmail dot com> --- Reduced C++ code seems to be: extern fprintf(char); struct string { string(char); }; struct { call(); replace(string); } vsllib; struct ListNode { ListNode(); }; struct TestNode { TestNode(int); }; typedef struct { *node; } YYSTYPE; int vsldebug, VSLLib_parse_vsln, VSLLib_parse_vslvsp_4294967293_0_0; VSLLib_parse() { YYSTYPE *vslvsp; vslnewstate: switch (VSLLib_parse_vsln) { case 13: vslvsp = 0; case 6: string(""); case 35: delete vslvsp; VSLLib_parse_vslvsp_4294967293_0_0 &&vslvsp[0].node ? new ListNode : 0; case 72: delete vslvsp; case 75: vslvsp ? vsllib.call() : 0; case 9: vsllib.call(); case 1: vsllib.call(); case 3: vsllib.call(); case 5: vsllib.call(); case 7: vsllib.call(); case 0: vsllib.call(); case 2: VSLLib_parse_vslvsp_4294967293_0_0 &&vslvsp[0].node ? new TestNode(new int) : 0; string func_name = vsllib.replace(func_name) && vsllib.replace(0); delete vslvsp; } ++vslvsp; if (vsldebug) fprintf(""); goto vslnewstate; }
next prev parent reply other threads:[~2022-09-06 21:39 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-06 17:35 [Bug c++/106862] New: " dcb314 at hotmail dot com 2022-09-06 17:55 ` [Bug tree-optimization/106862] " dcb314 at hotmail dot com 2022-09-06 21:39 ` dcb314 at hotmail dot com [this message] 2022-09-07 8:28 ` dcb314 at hotmail dot com 2022-09-07 8:55 ` 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-106862-4-Xlx7qhw1zI@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).