Davide Libenzi wrote:
> typedef union epoll_obj {
> void *ptr;
> __uint32_t u32[2];
> __uint64_t u64;
> } epoll_obj_t;
>
> I'm open to suggestions though. The "ptr" enable me to avoid wierd casts
> to avoid gcc screaming.
That makes more sense to me, because it will be fine to use `ptr' even
on 128-bit pointer machines when they arrive, yet preserves the
property that 64<->32 bit conversion functions don't need to reformat
the buffer when running 32-bit applications on a 64-bit CPU... even if
the 32-bit application uses the `ptr' field.
Did I just write that? :)
-- Jamie
-
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 : Sat Nov 23 2002 - 22:00:34 EST