Searched hist:a67ef0a77a6bf036275ca4365d251d34b92cfa78 (Results 1 – 1 of 1) sorted by relevance
| /freebsd/sys/amd64/include/ |
| H A D | cpufunc.h | diff a67ef0a77a6bf036275ca4365d251d34b92cfa78 Thu Mar 11 14:38:54 CET 2004 Bruce Evans <bde@FreeBSD.org> Don't implement anything in the ffs family in <machine/cpufunc.h>
in the non-_KERNEL case. This "fixes" applications that include
this "kernel-only" header and also include <strings.h> (or get
<strings.h> via the default _BSD_VISIBLE pollution in <string.h>.
In C++ there was a fatal error: the declaration specifies C linkage
but the implementation gives C++ linkage. In C there was only a
static/extern mismatch if the headers were included in a certain order
order, and a partially redundant declaration for all include orders;
gcc emits incomplete or wrong diagnostics for these, but only for
compiling with -Wsystem-headers and certain other warning options, so
the problem was usually not seen for C.
Ports breakage reported by: kris
diff a67ef0a77a6bf036275ca4365d251d34b92cfa78 Thu Mar 11 14:38:54 CET 2004 Bruce Evans <bde@FreeBSD.org> Don't implement anything in the ffs family in <machine/cpufunc.h>
in the non-_KERNEL case. This "fixes" applications that include
this "kernel-only" header and also include <strings.h> (or get
<strings.h> via the default _BSD_VISIBLE pollution in <string.h>.
In C++ there was a fatal error: the declaration specifies C linkage
but the implementation gives C++ linkage. In C there was only a
static/extern mismatch if the headers were included in a certain order
order, and a partially redundant declaration for all include orders;
gcc emits incomplete or wrong diagnostics for these, but only for
compiling with -Wsystem-headers and certain other warning options, so
the problem was usually not seen for C.
Ports breakage reported by: kris
|