public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/114554] In O2-3 optimization, this code runs in an infinite loop. Date: Tue, 02 Apr 2024 06:35:05 +0000 [thread overview] Message-ID: <bug-114554-4-r2Nv2HtDE2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114554-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114554 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Also didn't you read https://gcc.gnu.org/bugs/ or even what is mentioned on the bug entry web page? https://gcc.gnu.org/bugs/ says: Before reporting that GCC compiles your code incorrectly, compile it with gcc -Wall -Wextra and see whether this shows anything wrong with your code. Similarly, if compiling with -fno-strict-aliasing -fwrapv -fno-aggressive-loop-optimizations makes a difference, or if compiling with -fsanitize=undefined produces any run-time errors, then your code is probably not correct. bug entry web page (IN RED AND BOLD): Before reporting that GCC compiles your code incorrectly, compile it with gcc -Wall -Wextra and see whether this shows anything wrong with your code. Similarly, if compiling with -fno-strict-aliasing -fwrapv makes a difference, your code probably is not correct.
next prev parent reply other threads:[~2024-04-02 6:35 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-02 6:24 [Bug c/114554] New: " nmodnation at gmail dot com 2024-04-02 6:26 ` [Bug c/114554] " pinskia at gcc dot gnu.org 2024-04-02 6:28 ` pinskia at gcc dot gnu.org 2024-04-02 6:35 ` pinskia at gcc dot gnu.org [this message] 2024-04-02 6:45 ` nmodnation at gmail dot com
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-114554-4-r2Nv2HtDE2@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).