From: Jason Merrill <jason@redhat.com>
To: Jasmine Tang <tanghocle456@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [patch] PR 81271: gcc/cp/lex.c:116: wrong condition ?
Date: Wed, 24 Jan 2024 15:52:24 -0500 [thread overview]
Message-ID: <4e887d3d-581d-42cc-82dd-e5e2483f0d3d@redhat.com> (raw)
In-Reply-To: <CAP8tkpCH+FNXEFuRd2xzT_iDz-G5cCwQVg+qnwy9pph7JPo6Hw@mail.gmail.com>
On 1/24/24 00:57, Jasmine Tang wrote:
> Change the style from & to && to reflect boolean result with boolean
> operation (instead of bitwise operation)
>
> David Binderman 2017-07-01 13:24:44 UTC
>
> trunk/gcc/cp/lex.c:116]: (style) Boolean result is used in bitwise operation. Clarify expression with parentheses.
>
> Source code is
>
> gcc_checking_assert (!IDENTIFIER_KIND_BIT_2 (id)
> & !IDENTIFIER_KIND_BIT_1 (id)
> & !IDENTIFIER_KIND_BIT_0 (id));
>
> Maybe better code
>
> gcc_checking_assert (!IDENTIFIER_KIND_BIT_2 (id)
> && !IDENTIFIER_KIND_BIT_1 (id)
> && !IDENTIFIER_KIND_BIT_0 (id));
>
Since the _BIT_n macros all produce either 0 or 1, bitwise & has the
same meaning as &&, except possibly faster because it doesn't involve
the shortcut semantics of &&.
I notice the warning suggests "Clarify expression with parentheses." I
suspect that means along the lines of IDENTIFIER_KEYWORD_P and such in
cp-tree.h, where the ! expression is parenthesized:
> #define IDENTIFIER_KEYWORD_P(NODE) \
> ((!IDENTIFIER_KIND_BIT_2 (NODE)) \
> & (!IDENTIFIER_KIND_BIT_1 (NODE)) \
> & IDENTIFIER_KIND_BIT_0 (NODE))
Does doing that quiet the warning?
Jason
next prev parent reply other threads:[~2024-01-24 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 5:57 Jasmine Tang
2024-01-24 20:52 ` Jason Merrill [this message]
2024-01-24 6:02 Jasmine Tang
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=4e887d3d-581d-42cc-82dd-e5e2483f0d3d@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tanghocle456@gmail.com \
/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).