Hi,
I just had a case where proto_ops.setsockopt seems to have the same signature
as the function driver_setsockopt, but gcc barfs.
struct proto_ops p = {
.setsockopt = driver_setsockopt,
};
227600/vsock-only/linux/af_vsock.c:361: warning: initialization from
incompatible pointer type
it would be nice if it told which type was used, and which type was expected,
because I am pretty sure the compiler is right and I just did not find the
right source file.
--
Summary: init from incompatible pointer type: verbosity
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jengelh at medozas dot de
GCC build triplet: any
GCC host triplet: any
GCC target triplet: any
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43664
