public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/95971] [10 regression] Optimizer converts a false boolean value into a true boolean value
Date: Mon, 29 Jun 2020 21:30:25 +0000	[thread overview]
Message-ID: <bug-95971-4-AkJg5y3zkR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95971-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95971

--- Comment #11 from Marc Glisse <glisse at gcc dot gnu.org> ---
        while(!a.isZero());

that doesn't look like something you would find in real code. Are you waiting
for a different thread to modify a? Then you should use an atomic operation.
Are you waiting for the hardware to change something? Use volatile. Do you
really want an infinite loop? Spell it out if(!a.isZero())for(;;);

  parent reply	other threads:[~2020-06-29 21:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 16:19 [Bug other/95971] New: " 0xe2.0x9a.0x9b at gmail dot com
2020-06-29 16:20 ` [Bug other/95971] " 0xe2.0x9a.0x9b at gmail dot com
2020-06-29 16:20 ` 0xe2.0x9a.0x9b at gmail dot com
2020-06-29 16:20 ` 0xe2.0x9a.0x9b at gmail dot com
2020-06-29 17:43 ` marxin at gcc dot gnu.org
2020-06-29 18:05 ` 0xe2.0x9a.0x9b at gmail dot com
2020-06-29 18:27 ` marxin at gcc dot gnu.org
2020-06-29 18:44 ` 0xe2.0x9a.0x9b at gmail dot com
2020-06-29 18:50 ` marxin at gcc dot gnu.org
2020-06-29 19:15 ` 0xe2.0x9a.0x9b at gmail dot com
2020-06-29 20:50 ` 0xe2.0x9a.0x9b at gmail dot com
2020-06-29 21:30 ` glisse at gcc dot gnu.org [this message]
2020-06-29 21:43 ` 0xe2.0x9a.0x9b 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-95971-4-AkJg5y3zkR@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).