This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/77513] -Wzero-as-null-pointer-constant vs 0, nullptr, NULL and __null
- From: "petschy at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 07 Sep 2016 12:37:54 +0000
- Subject: [Bug c++/77513] -Wzero-as-null-pointer-constant vs 0, nullptr, NULL and __null
- Auto-submitted: auto-generated
- References: <bug-77513-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77513
--- Comment #2 from petschy at gmail dot com ---
I don't want to enable them. The problem is not with too little but too many
warnings.
A snippet from one of the problematic files:
{ NULL, NULL, false, false }
is preprocessed to
{
# 62 "AdsPlugin.cpp" 3 4
__null
# 62 "AdsPlugin.cpp"
,
# 62 "AdsPlugin.cpp" 3 4
__null
# 62 "AdsPlugin.cpp"
, false, false }
};
Here I see the same flags, yet for these two NULLs gcc warns.