public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <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
Date: Wed, 08 Mar 2023 12:06:37 +0000	[thread overview]
Message-ID: <bug-109031-4-l03wpzNAge@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 #8 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to David Binderman from comment #7)
> (In reply to David Binderman from comment #4)
> > Created attachment 54596 [details]
> > C source code
> > 
> > After 3 hours further reduction.
> 
> I am struggling with further reduction. My bash knowledge is short.
> 
> My cvise script is:
> 
> /usr/bin/gcc -w -Werror=implicit bug892.c \
> && (./a.out 1 > 1) \
> && /home/dcb36/gcc/results/bin/gcc -w -O2 -fno-strict-aliasing bug892.c 
> \
> && (./a.out 1 > 2) \
> && diff 1 2; \
> 
> but then if diff returns 1, the script should return 0 and
> if diff returns 0, then the script should return 1.

You can take an inspiration here:
https://github.com/marxin/gcc-util/blob/master/bisect/reduce.sh

and you can use multiple `if` statements.

  parent reply	other threads:[~2023-03-08 12:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 21:26 [Bug c/109031] New: " 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 [this message]
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
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-l03wpzNAge@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).