This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/61276] warn about possible coding errors with logical not (!)
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 21 May 2014 17:15:51 +0000
- Subject: [Bug c++/61276] warn about possible coding errors with logical not (!)
- Auto-submitted: auto-generated
- References: <bug-61276-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61276
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Manuel LÃpez-IbÃÃez from comment #3)
> Just to mention that I cloned PR 61271 to not forget about implementing the
> warning once the problematic code is fixed. So this PR should be about
> implementing the warning, rather than fixing any particular problems.
Oops, sorry I didn't read it properly!
(In reply to Manuel LÃpez-IbÃÃez from comment #4)
> Can't Google/RedHat/Oracle/Suse/Mentor/ARM/Linaro poll resources and have at
> least one GCC developer committed to diagnostic issues? Just a single one
> full-time developer will make such a huge difference.
Although I agree with the sentiment it's just not practical, a full-time
developer can't really have seven different employers.