Re: [PATCH] x86 byteorder.h: use __asm__/__inline__ for userspace

H. Peter Anvin
2008-12-27T19:24:04Z

Mike Frysinger wrote:
>
> {su}{8,16,32,64} doesnt matter too much to me vs {u,}int_t{8,16,32,64}_t. as
> long as people stop using __{su}{8,16,32,64}. using the latter though does
> mean headers will more likely be "just usable" w/out needing linux/types.h
> include. but then people would be forced to include stdint.h or similar
> before a linux header ... and that sucks.
>

That is a total non-starter. This would mean that the C library itself
cannot use these headers without exporting additional symbols into the
namespace, *WHICH IT IS NOT ALLOWED TO DO*.

> unless of course we start adding appropriate C library includes for
> !__KERNEL__ ... i'd love that personally
>
>> and bool into the appropriate __{su}{8,16,32,64}
>> types and _Bool.
>
> i dont get your bool comment. the "bool" type is already a standard type.
> there is no conversion needed.

Only if <stdbool.h> is included. Again, see previous statement.

-hpa

--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.