On Tue, 10 Oct 2017, Martin Sebor wrote: > The ideal solution for 1) would be a function pointer that can > never be used to call a function (i.e., the void* equivalent > for functions).[X]
I don't think that's relevant. The normal idiom for this in modern C code, if not just using void *, is void (*) (void), and since the warning is supposed to be avoiding excessive false positives and detecting the cases that are likely to be used for ABI-incompatible calls, the warning should allow void (*) (void) there. -- Joseph S. Myers jos...@codesourcery.com
