public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nok.raven at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101537] -Wconversion false positive in ternary
Date: Sun, 08 Aug 2021 15:15:40 +0000	[thread overview]
Message-ID: <bug-101537-4-IA6L5BTDZv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101537-4@http.gcc.gnu.org/bugzilla/>

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

Nikita Kniazev <nok.raven at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nok.raven at gmail dot com

--- Comment #1 from Nikita Kniazev <nok.raven at gmail dot com> ---
int foo(unsigned char x, bool f) {
    x |= f ? 1 : 0; // warning
    return x;
}

int bar(unsigned char x, bool f) {
    x = x | f ? 1 : 0; // no warning
    return x;
}

it also warns only for self-operators

  reply	other threads:[~2021-08-08 15:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 17:41 [Bug c++/101537] New: " me at xenu dot pl
2021-08-08 15:15 ` nok.raven at gmail dot com [this message]
2021-08-12 23:47 ` [Bug c/101537] -Wconversion false positive in ternary and |= pinskia at gcc dot gnu.org
2021-12-31 17:25 ` thomas at habets dot se
2021-12-31 22:34 ` jakub at gcc dot gnu.org
2022-01-03 11:52 ` jakub at gcc dot gnu.org
2022-01-11 18:15 ` cvs-commit at gcc dot gnu.org
2022-01-24  9:21 ` cvs-commit at gcc dot gnu.org
2022-05-10  8:22 ` cvs-commit at gcc dot gnu.org
2023-06-29 15:31 ` wolter.hellmundvega at tevva 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-101537-4-IA6L5BTDZv@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).