public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/111210] Wrong code at -Os on x86_64-linux-gnu since r12-4849-gf19791565d7 Date: Mon, 28 Aug 2023 12:55:57 +0000 [thread overview] Message-ID: <bug-111210-4-YitC9gxiNd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111210-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111210 --- Comment #4 from Alexander Monakov <amonakov at gcc dot gnu.org> --- The testcase is small enough to notice the issue by inspection. Note that you get the "expected" answer with -fno-strict-aliasing, and as explained in https://gcc.gnu.org/bugs/ it is one of the things you should check when submitting a bugreport: 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.
next prev parent reply other threads:[~2023-08-28 12:55 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-28 7:13 [Bug c/111210] New: " shaohua.li at inf dot ethz.ch 2023-08-28 7:29 ` [Bug c/111210] " amonakov at gcc dot gnu.org 2023-08-28 12:46 ` shaohua.li at inf dot ethz.ch 2023-08-28 12:50 ` xry111 at gcc dot gnu.org 2023-08-28 12:55 ` amonakov at gcc dot gnu.org [this message] 2023-08-28 12:58 ` shaohua.li at inf dot ethz.ch
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-111210-4-YitC9gxiNd@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).