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 c/114052] [11/12/13/14 Regression] Wrong code at -O2 for well-defined infinite loop
Date: Thu, 22 Feb 2024 10:56:30 +0000	[thread overview]
Message-ID: <bug-114052-4-6CwDbVWtPu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114052-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114052

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org
   Target Milestone|---                         |11.5
             Status|UNCONFIRMED                 |NEW
            Summary|Wrong code at -O2 for       |[11/12/13/14 Regression]
                   |well-defined infinite loop  |Wrong code at -O2 for
                   |                            |well-defined infinite loop
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2024-02-22

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r8-5245-g5b0c69ae65b713ab68202af20dae9dca533d39cf

  reply	other threads:[~2024-02-22 10:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 10:46 [Bug c/114052] New: " maxdamantus at gmail dot com
2024-02-22 10:56 ` jakub at gcc dot gnu.org [this message]
2024-02-22 10:56 ` [Bug c/114052] [11/12/13/14 Regression] " jakub at gcc dot gnu.org
2024-02-22 11:11 ` sjames at gcc dot gnu.org
2024-02-22 12:18 ` [Bug tree-optimization/114052] " rguenth at gcc dot gnu.org
2024-02-22 13:08 ` rguenth at gcc dot gnu.org
2024-02-22 13:54 ` hubicka at gcc dot gnu.org
2024-02-22 14:08 ` rguenth at gcc dot gnu.org
2024-02-22 14:20 ` hubicka at ucw dot cz
2024-04-05 12:03 ` 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-114052-4-6CwDbVWtPu@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).