public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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 since r13-3875
Date: Thu, 09 Feb 2023 14:32:26 +0000	[thread overview]
Message-ID: <bug-108737-4-Y4U8HzPxPO@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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1
                 CC|                            |jakub at gcc dot gnu.org
            Summary|[13 Regression] Apparent    |[13 Regression] Apparent
                   |miscompile of infinite loop |miscompile of infinite loop
                   |on gcc trunk in cddce2 pass |on gcc trunk in cddce2 pass
                   |                            |since r13-3875
           Keywords|needs-bisection             |

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The foo definition could be e.g.
extern "C" void exit (int);
int foo() {
  static int cnt;
  if (cnt++ == 0)
    return 1;
  if (cnt > 42)
    exit (0);
  return 0;
}

Yes, if first invocation of foo returns 0, then it would invoke UB in C++, but
if it returns non-zero and isn't const or pure, it can't be optimized this way.

Started with r13-3875-g9e11ceef165bc074c2fc85b8ddece606b24e710b

  parent reply	other threads:[~2023-02-09 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  7:44 [Bug c++/108737] New: Apparent miscompile of infinite loop on gcc trunk in cddce2 pass njs at pobox dot com
2023-02-09 14:04 ` [Bug tree-optimization/108737] [13 Regression] " rguenth at gcc dot gnu.org
2023-02-09 14:32 ` jakub at gcc dot gnu.org [this message]
2023-02-09 14:38 ` [Bug tree-optimization/108737] [13 Regression] Apparent miscompile of infinite loop on gcc trunk in cddce2 pass since r13-3875 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-Y4U8HzPxPO@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: link
Be 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).