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 c/108718] [10/11/12/13 Regression] csmith: possible bad code with -O2
Date: Wed, 08 Feb 2023 14:12:47 +0000 [thread overview]
Message-ID: <bug-108718-4-RNXX5EJkae@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108718-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108718
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Summary|csmith: possible bad code |[10/11/12/13 Regression]
|with -O2 |csmith: possible bad code
| |with -O2
Target Milestone|--- |10.5
CC| |rguenth at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Seems the testcase allows to be called with argument 1 and in that case it
prints verbose output, which between r11-1351^ and r11-1351 at -O2 differs
starting with:
--- 1 2023-02-08 09:10:13.000000000 -0500
+++ 2 2023-02-08 09:10:22.000000000 -0500
@@ -48,1210 +48,1210 @@ index = [2][2]
index = [2][3]
...checksum after hashing g_5[i][j].f4 : ADCB0EBF
index = [2][4]
-...checksum after hashing g_5[i][j].f4 : C953D56F
+...checksum after hashing g_5[i][j].f4 : 367D9AB8
index = [2][5]
-...checksum after hashing g_5[i][j].f4 : 37A7B1F1
+...checksum after hashing g_5[i][j].f4 : 7EFE68AE
index = [2][6]
-...checksum after hashing g_5[i][j].f4 : A0619D0A
+...checksum after hashing g_5[i][j].f4 : 6C5E59F1
The only changes in optimized dump as well as in assembly are in main.
next prev parent reply other threads:[~2023-02-08 14:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 13:53 [Bug c/108718] New: " dcb314 at hotmail dot com
2023-02-08 14:06 ` [Bug c/108718] " jakub at gcc dot gnu.org
2023-02-08 14:12 ` jakub at gcc dot gnu.org [this message]
2023-02-08 17:06 ` [Bug c/108718] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2023-02-09 15:10 ` dcb314 at hotmail dot com
2023-02-09 20:12 ` jakub at gcc dot gnu.org
2023-02-10 10:19 ` rguenth at gcc dot gnu.org
2023-02-10 17:07 ` dcb314 at hotmail dot com
2023-02-15 8:17 ` dcb314 at hotmail dot com
2023-02-15 10:29 ` dcb314 at hotmail dot com
2023-02-15 10:39 ` marxin at gcc dot gnu.org
2023-02-15 17:00 ` dcb314 at hotmail dot com
2023-02-16 12:59 ` jakub 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-108718-4-RNXX5EJkae@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).