[Bug c++/91187] Is it possible to make -Wzero-as-null-pointer-constant learn about extern "C"?

2020-01-28 Thread harald at gigawatt dot nl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91187 --- Comment #9 from Harald van Dijk --- (In reply to Jonathan Wakely from comment #8) > (In reply to Albert Astals Cid from comment #0) > > #define Z_NULL 0 > > N.B. this is actually a bug. Using Z_NULL where a null pointer is expected > might

[Bug c++/91187] Is it possible to make -Wzero-as-null-pointer-constant learn about extern "C"?

2020-01-28 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91187 --- Comment #8 from Jonathan Wakely --- (In reply to Albert Astals Cid from comment #0) > #define Z_NULL 0 N.B. this is actually a bug. Using Z_NULL where a null pointer is expected might cause bugs e.g. execl("foo", "foo", Z_NULL) can pass a

[Bug c++/91187] Is it possible to make -Wzero-as-null-pointer-constant learn about extern "C"?

2020-01-28 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91187 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/91187] Is it possible to make -Wzero-as-null-pointer-constant learn about extern "C"?

2019-07-17 Thread harald at gigawatt dot nl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91187 --- Comment #7 from Harald van Dijk --- (In reply to Albert Astals Cid from comment #5) > (In reply to Harald van Dijk from comment #3) > > If the header files cannot be modified, the -isystem command-line option > > also causes included files

[Bug c++/91187] Is it possible to make -Wzero-as-null-pointer-constant learn about extern "C"?

2019-07-17 Thread aacid at kde dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91187 --- Comment #6 from Albert Astals Cid --- Created attachment 46609 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46609=edit the said main-glib.cpp file well the line has to be g++ -c -Wzero-as-null-pointer-constant main-glib.cpp -isystem

[Bug c++/91187] Is it possible to make -Wzero-as-null-pointer-constant learn about extern "C"?

2019-07-17 Thread aacid at kde dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91187 --- Comment #5 from Albert Astals Cid --- (In reply to Harald van Dijk from comment #3) > If the header files cannot be modified, the -isystem command-line option > also causes included files to be treated as system headers where warnings > are

[Bug c++/91187] Is it possible to make -Wzero-as-null-pointer-constant learn about extern "C"?

2019-07-17 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91187 --- Comment #4 from Jonathan Wakely --- (In reply to Eric Gallager from comment #2) > maybe try putting #pragma GCC system_header in your headers? idk Please no, that's for marking a header as part of "the implementation" not a

[Bug c++/91187] Is it possible to make -Wzero-as-null-pointer-constant learn about extern "C"?

2019-07-17 Thread harald at gigawatt dot nl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91187 Harald van Dijk changed: What|Removed |Added CC||harald at gigawatt dot nl --- Comment

[Bug c++/91187] Is it possible to make -Wzero-as-null-pointer-constant learn about extern "C"?

2019-07-16 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91187 Eric Gallager changed: What|Removed |Added Keywords||diagnostic CC|

[Bug c++/91187] Is it possible to make -Wzero-as-null-pointer-constant learn about extern "C"?

2019-07-16 Thread aacid at kde dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91187 --- Comment #1 from Albert Astals Cid --- This is with gcc version 9.1.0