public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93041] GCC 10 removes an infinite loop and causes a null pointer to dereferenced
Date: Tue, 09 Apr 2024 08:22:25 +0000	[thread overview]
Message-ID: <bug-93041-4-M9oJNIoKQd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93041-4@http.gcc.gnu.org/bugzilla/>

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

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xry111 at gcc dot gnu.org

--- Comment #12 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Ganton from comment #11)
> A related assigned task is:
> [C++26] P2809R3 - Trivial infinite loops are not undefined behavior
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114462

Note that even with P2809R3 the test case in this ticket is still invalid, as
explained in comment 9.

      parent reply	other threads:[~2024-04-09  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93041-4@http.gcc.gnu.org/bugzilla/>
2024-03-21 21:48 ` pinskia at gcc dot gnu.org
2024-03-21 21:48 ` pinskia at gcc dot gnu.org
2024-03-21 21:48 ` pinskia at gcc dot gnu.org
2024-03-21 22:01 ` jakub at gcc dot gnu.org
2024-04-07 22:28 ` pinskia at gcc dot gnu.org
2024-04-08 20:10 ` kubry at gmx dot com
2024-04-09  8:22 ` xry111 at gcc dot gnu.org [this message]

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-93041-4-M9oJNIoKQd@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).