Messages in this thread | | | From | "[MOc]cda*mirabilos" <> | Subject | Re: Typedefs / gcc / HIGHMEM | Date | Sun, 9 Dec 2001 00:48:17 -0000 |
| |
> Ha, I always wondered what this u64 is all about :-) > Honestly, this whole datatyping is gone completely mad since the 16-32 > bit change. In my opinion > byte is 8 bit > short is 16 bit > long is 32 bit > <callwhatyouwant> is 64 bit (I propose long2 for expression of bitsize > long * 2). > <callwhatyouwant2> is 128 bit (Ha, right I would call it long4)
There's the bit types: u_int8_t (unsigned char) u_int16_t (unsigned short int) ...
int8_t (signed char) int16_t (signed short int) ...
size_t and register_t If I understand these correctly, size_t is the size of a pointer (ptrdiff_t on linux?) and register_t is signed size_t.
These are common along GNU and BSD systems, just #ifdef __BIT_TYPES_DEFINED__ For porting issues, many Win32 headers have them as now, and for DOS16 and DOS32 they're easy.
> char is the standard representation of chars in the corresponding > environment, currently sizeof(byte). > int is the same and should move from 16 bit to 32 bit to 64 bit > depending on the machine. I mean whats the use of an int register in a > 64bit environment, when datatype int is only of size 32 bit? This is > _shit_.
ACK.
-mirabilos
- 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/
| |