public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108737] [13 Regression] Apparent miscompile of infinite loop on gcc trunk in cddce2 pass Date: Thu, 09 Feb 2023 14:04:57 +0000 [thread overview] Message-ID: <bug-108737-4-uKkcWpUipG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108737-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108737 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Apparent miscompile of |[13 Regression] Apparent |infinite loop on gcc trunk |miscompile of infinite loop |in cddce2 pass |on gcc trunk in cddce2 pass Last reconfirmed| |2023-02-09 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Target Milestone|--- |13.0 Keywords| |needs-bisection Component|c++ |tree-optimization Version|unknown |13.0 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- C++ has the forward progress guarantee, in case 'x' is false there's an endless loop which is undefined behavior. Now, the same happens with C and with -fno-finite-loops, so there's something amiss here. -funswitch-loops is necessary, but GCC 12 doesn't seem to be affected ...
next prev parent reply other threads:[~2023-02-09 14:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-09 7:44 [Bug c++/108737] New: " njs at pobox dot com 2023-02-09 14:04 ` rguenth at gcc dot gnu.org [this message] 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-uKkcWpUipG@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).