public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "njs at pobox dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108737] New: Apparent miscompile of infinite loop on gcc trunk in cddce2 pass Date: Thu, 09 Feb 2023 07:44:26 +0000 [thread overview] Message-ID: <bug-108737-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108737 Bug ID: 108737 Summary: Apparent miscompile of infinite loop on gcc trunk in cddce2 pass Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: njs at pobox dot com Target Milestone: --- There's a meme going around about strange compilation outputs caused infinite-loop-related UB, and while discussing it a friend stumbled on this weird behavior: https://godbolt.org/z/qfj1jabMW C++ code is: extern int foo(); void blah() { int x = foo(); while (1) { if(x) foo(); } } When compiled with whatever "gcc trunk" means on compiler explorer, and with -O3 (but not -O2), as C++ (but not C), then gcc reduces this to a single call to `foo()` followed by an empty infinite loop: blah(): sub rsp, 8 call foo() .L2: jmp .L2 As far as I can tell, there's no UB here -- 'foo' being extern means it might do anything, and infinite loops with side-effects are well-defined in C++. So this seems like a straight-up optimizer bug? Poking through the pass analysis in CE, it looks like the output of "unrolljam (tree)" is still correct, but then the output of the next pass "cddce2 (tree)" has deleted everything. Somehow it concludes that the hoisted `if` can be eliminated? idgi.
next reply other threads:[~2023-02-09 7:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-09 7:44 njs at pobox dot com [this message] 2023-02-09 14:04 ` [Bug tree-optimization/108737] [13 Regression] " rguenth at gcc dot gnu.org 2023-02-09 14:32 ` [Bug tree-optimization/108737] [13 Regression] Apparent miscompile of infinite loop on gcc trunk in cddce2 pass since r13-3875 jakub at gcc dot gnu.org 2023-02-09 14:38 ` rguenth at gcc dot gnu.org 2023-02-10 9:25 ` rguenth at gcc dot gnu.org 2023-02-13 7:28 ` 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-108737-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).