https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
--- Comment #12 from uecker at gcc dot gnu.org ---
I filed PR117687 for the other cases.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
--- Comment #11 from Joseph S. Myers ---
This does not currently warn about zero of enum, bool or _BitInt type except in
contexts where integer promotions result in bool being promoted to int before
the diagnostic applies.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
--- Comment #10 from Alejandro Colomar ---
Do we warn about enum/_Bool (PR112556) with this? My computer with which I
work with GCC is having a hardware failure and I can't use it until 3 weeks
from now when a new piece arrives.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
Sam James changed:
What|Removed |Added
Target Milestone|--- |15.0
Assignee|unassigned at gcc d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
--- Comment #8 from Alejandro Colomar ---
Several years don't buy us much. I think having it for 1 release will already
make it better. Further than 1 release gives us not much value; especially if
there's no release notes that say that it wil
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
--- Comment #7 from Joseph S. Myers ---
How about the gnulib manywarnings module for a few years first, which would
cover various gnulib-using projects that like a high level of warnings, and
then consider -Wextra?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
--- Comment #6 from Alejandro Colomar ---
Hmm, okay, Wextra as a first step makes sense.
How about one release in Wextra, and then move it to Wall?
As for ISO C, I'm not sure if ISO is a good place to start the deprecation. I
don't like ISO i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
--- Comment #5 from uecker at gcc dot gnu.org ---
While I personally would like to have this warning in -Wall, and also want to
see 0 as null pointer constant be deprecated, I think it is too early. At this
time, it is not deprecated (I have a d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
--- Comment #4 from Alejandro Colomar ---
Since I would like to officially deprecate 0 as a null pointer constant, it
would be good if we put it in -Wall. Does it make sense?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
--- Comment #3 from GCC Commits ---
The master branch has been updated by Martin Uecker :
https://gcc.gnu.org/g:236c0829ee21a179c81b83f0d7f112ca23c47a4d
commit r15-5191-g236c0829ee21a179c81b83f0d7f112ca23c47a4d
Author: Martin Uecker
Date: S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
uecker at gcc dot gnu.org changed:
What|Removed |Added
Keywords||patch
--- Comment #2 from ue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117059
uecker at gcc dot gnu.org changed:
What|Removed |Added
CC||uecker at gcc dot gnu.org
12 matches
Mail list logo