public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marc.glisse at normalesup dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/44949] extend Wparentheses from & to &=
Date: Sat, 06 Aug 2011 20:50:00 -0000 [thread overview]
Message-ID: <bug-44949-4-fUDpBRFEdB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44949-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44949
--- Comment #1 from Marc Glisse <marc.glisse at normalesup dot org> 2011-08-06 20:49:40 UTC ---
Created attachment 24935
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24935
hack
It is an easy enough hack to call the Wparentheses code for &= and others (the
warning says "&" instead of "&=", it isn't a clean patch) so I can test on real
code. And it seems painful. It warns on code like: a |= b & c; where it is
quite clear we could never intend (a|=b)&c;. Restricting the warning to the
case where the result of the expression is used should improve things, except
that I don't know how to access that information...
next parent reply other threads:[~2011-08-06 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-44949-4@http.gcc.gnu.org/bugzilla/>
2011-08-06 20:50 ` marc.glisse at normalesup dot org [this message]
2023-07-20 17:02 ` gsmecher at threespeedlogic 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-44949-4-fUDpBRFEdB@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).