public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing since r13-254-gdd3c7873a61019e9 Date: Thu, 09 Mar 2023 09:45:46 +0000 [thread overview] Message-ID: <bug-109031-4-jgjSZ0DL0W@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109031-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031 --- Comment #24 from David Binderman <dcb314 at hotmail dot com> --- I tried experimenting with the flags that change -O1 into -O2 and got this: $ for i in ~/gcc/results.202205*/bin/gcc; do echo $i; $i -w -ftrivial-auto-var-init=zero -O1 -fno-strict-aliasing bug892.c && (./a.out 1 | fgrep g_50); done /home/dcb36/gcc/results.20220501/bin/gcc ...checksum after hashing g_50 : 646CF84D /home/dcb36/gcc/results.20220508/bin/gcc ...checksum after hashing g_50 : 646CF84D /home/dcb36/gcc/results.20220515/bin/gcc ...checksum after hashing g_50 : 646CF84D $ for i in ~/gcc/results.202205*/bin/gcc; do echo $i; $i -w -ftrivial-auto-var-init=zero -O1 -fcode-hoisting -fno-strict-aliasing bug892.c && (./a.out 1 | fgrep g_50); done /home/dcb36/gcc/results.20220501/bin/gcc ...checksum after hashing g_50 : 646CF84D /home/dcb36/gcc/results.20220508/bin/gcc ...checksum after hashing g_50 : 646CF84D /home/dcb36/gcc/results.20220515/bin/gcc ...checksum after hashing g_50 : C21BF3F9 so the -fcode-hoisting looks to be part of the problem.
next prev parent reply other threads:[~2023-03-09 9:45 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-05 21:26 [Bug c/109031] New: csmith: possible bad code with -O2 -fno-strict-aliasing dcb314 at hotmail dot com 2023-03-06 15:05 ` [Bug middle-end/109031] " dcb314 at hotmail dot com 2023-03-06 16:03 ` dcb314 at hotmail dot com 2023-03-06 17:43 ` dcb314 at hotmail dot com 2023-03-06 20:33 ` dcb314 at hotmail dot com 2023-03-06 20:41 ` pinskia at gcc dot gnu.org 2023-03-07 0:10 ` pinskia at gcc dot gnu.org 2023-03-08 11:10 ` dcb314 at hotmail dot com 2023-03-08 12:06 ` marxin at gcc dot gnu.org 2023-03-08 13:39 ` dcb314 at hotmail dot com 2023-03-08 13:43 ` marxin at gcc dot gnu.org 2023-03-08 13:56 ` dcb314 at hotmail dot com 2023-03-08 14:01 ` marxin at gcc dot gnu.org 2023-03-08 14:08 ` dcb314 at hotmail dot com 2023-03-08 14:10 ` marxin at gcc dot gnu.org 2023-03-08 14:16 ` dcb314 at hotmail dot com 2023-03-08 14:24 ` marxin at gcc dot gnu.org 2023-03-08 16:45 ` dcb314 at hotmail dot com 2023-03-08 17:12 ` dcb314 at hotmail dot com 2023-03-09 8:44 ` marxin at gcc dot gnu.org 2023-03-09 8:48 ` jakub at gcc dot gnu.org 2023-03-09 8:59 ` marxin at gcc dot gnu.org 2023-03-09 9:25 ` dcb314 at hotmail dot com 2023-03-09 9:41 ` [Bug middle-end/109031] csmith: possible bad code with -O2 -fno-strict-aliasing since r13-254-gdd3c7873a61019e9 marxin at gcc dot gnu.org 2023-03-09 9:45 ` dcb314 at hotmail dot com [this message] 2023-03-09 10:18 ` marxin at gcc dot gnu.org 2023-03-09 10:20 ` marxin at gcc dot gnu.org 2023-03-09 10:29 ` marxin at gcc dot gnu.org 2023-03-09 10:35 ` marxin at gcc dot gnu.org 2023-03-09 13:41 ` roger at nextmovesoftware dot com 2023-03-09 14:25 ` jakub at gcc dot gnu.org 2023-03-12 22:55 ` cvs-commit at gcc dot gnu.org 2023-03-14 7:33 ` roger at nextmovesoftware 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-109031-4-jgjSZ0DL0W@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).