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 middle-end/93041] GCC 10 removes an infinite loop and causes a null pointer to dereferenced Date: Thu, 21 Mar 2024 22:01:36 +0000 [thread overview] Message-ID: <bug-93041-4-CaFjeK8YRZ@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Note, C++26 will likely vote in tomorrow https://wg21.link/P2809R3 a change where loops like for (;;); or while (true) ; and similar will not be UB anymore. Though the loops in this PR and the dups aren't like that anyway and I think we already treat unconditional loops as infinite even with -ffinite-loops.
next prev parent reply other threads:[~2024-03-21 22:01 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 [this message] 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
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-CaFjeK8YRZ@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).