On Fri, Aug 31, 2018 at 02:10:12PM +0100, Roy Marples wrote:
The function is currently marked as __printflike.
If I re-enable the warning gcc warns me that it should be marked as
__sysloglike .... because it calls syslog. If I change it to __sysloglike
then it warns me that it should be __printflike because it also uses
vfprintf.
Ah, I see. So this is a bug, gcc should not warn if a __printflike function
calls a __sysloglike one, as one is strictly a superclass of the others -
or am I missing some hidden difference?