Message ID | alpine.DEB.2.10.1503062326580.9654@digraph.polyomino.org.uk |
---|---|
State | New |
Headers | show |
I think it's fine if it facilitates verbatim code-sharing. It's not really different from the kind of stuff we do in files that we want to share with gnulib. It wouldn't hurt to add some comments.
On 06 Mar 2015 23:28, Joseph Myers wrote: > What do people think about the principle of including such > conditionals? I think one will also be needed for zero-initialization > in _FP_DECL and _FP_FRAC_DECL_* (where Linux kernel functions may do > various operations with different sorts of unpacking and packing, so > it's not obvious to the compiler that the packing always only uses the > fields that were initialized, but the glibc and libgcc use of separate > functions for each operation avoids this issue). For other > differences I hope to be able to avoid such conditionals. makes sense to me -mike
diff --git a/soft-fp/soft-fp.h b/soft-fp/soft-fp.h index d0171e3..156048b 100644 --- a/soft-fp/soft-fp.h +++ b/soft-fp/soft-fp.h @@ -34,6 +34,8 @@ #ifdef _LIBC # include <sfp-machine.h> +#elif defined __KERNEL__ +# include <asm/sfp-machine.h> #else # include "sfp-machine.h" #endif