[Bug c/78000] -Wimplicit-function-declaration inhibited with macro from system headers

[mpolacek at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78000

--- Comment #4 from Marek Polacek  ---
No, that won't work, there are some fails.

[Bug c/78000] -Wimplicit-function-declaration inhibited with macro from system headers

[mpolacek at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78000

Marek Polacek  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2016-10-31
 Ever confirmed|0   |1

--- Comment #3 from Marek Polacek  ---
I'm testing a patch to disable inhibiting such warnings for macros from system
headers globally.  I've failed to come up with anything better so far.

[Bug c/78000] -Wimplicit-function-declaration inhibited with macro from system headers

[mpolacek at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78000

Marek Polacek  changed:

   What|Removed |Added

 CC||mpolacek at gcc dot gnu.org

--- Comment #2 from Marek Polacek  ---
At least PR71613 is related.

[Bug c/78000] -Wimplicit-function-declaration inhibited with macro from system headers

[joseph at codesourcery dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78000

--- Comment #1 from joseph at codesourcery dot com  ---
As I've said before, we have to stop doing individual ad hoc fixes for 
bugs like this; there are too many of them.  We have to work out the 
general principles for which warnings should or should not be inhibited 
for macros from system headers (roughly, the question is whether the macro 
or its user is responsible for the warning) and then design APIs that make 
it easy to get it right for each individual warning - and review existing 
warnings systematically.  Failing that, disable inhibiting such warnings 
for macros from system headers globally.