https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90885
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-06-14
CC| |egallager at gcc dot gnu.org
Blocks| |87403
Ever confirmed|0 |1
--- Comment #9 from Eric Gallager <egallager at gcc dot gnu.org> ---
Confirmed. More discussion from that thread about possible heuristics for the
warning: https://twitter.com/elwoz/status/1139522678396784642
* restricting it to just decimal literals probably makes sense, if someone is
using the 0x or 0b prefix, they probably are in fact intending to do
bit-twiddling with xor
* the "not from the expansion of <iso646.h>’s xor macro" criterion I can see
possibly being a difficulty, due to how many other bugs there are about gcc's
handling of macros from system headers...
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403
[Bug 87403] [Meta-bug] Issues that suggest a new warning
