Steve French <smfrench@austin.rr.com> said:
> Although it fixes it for building on 32 bit architectures, won't changing
>
>
> __u64 uid = 0xFFFFFFFFFFFFFFFF;
> to
>
> __u64 uid = 0xFFFFFFFFFFFFFFFFULL;
>
> generate a type mismatch warning on ppc64 and similar 64 bit
> architecutres since __u64 is not a unsigned long long on ppc64
> (it is unsigned long)? My gut reaction is to just ingore the three
> places that cause warnings and the remaining two places that cause
> signed/unsigned compare warnings of unsigned int local variables
> to #defined literals (which presumably are treated as signed by default).
Be careful, the value will get shoehorned into 4 bytes to make the int
constant, which is then assigned to the __u64.
-- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:32 EST