Tomas Carnecky wrote:
Alexey Starikovskiy wrote:
Moore, Robert wrote:
I think one of the reasons we introduced ACPI_NATIVE_UINT is that "int"
is in fact not "native" under all compilation models.
Here is the table from actypes.h
* Datatype LP64 ILP64 LLP64 ILP32 LP32 16bit
* char 8 8 8 8 8 8
* short 16 16 16 16 16 16
* _int32 32
* int 32 64 32 32 16 16
* long 64 64 32 32 32 32
* long long 64 64
* pointer 64 64 64 32 32 32
Sorry, what do you mean by "not native" ?
sizeof(int) != sizeof(void *) or something else?
On Linux that is not true!
What is not true? Meaning of "native" in our not-so-private discussion?
From wikipedia on '64-bit':
Many 64-bit compilers today use the LP64 model (including Solaris, AIX,
HP, Linux, Mac OS X, and IBM z/OS native compilers). Microsoft's VC++
compiler uses the LLP64 model.
So on Linux: sizeof(long) == sizeof(void *), that's why the kernel uses
'long' all over the place instead of 'int'.
These are well known facts, we were struggling through term definitions.
Regards,
Alex.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
