>> What determines 'true' 64 bit code?
>I would think sizeof(void_pointer) should be 8. It is also good if
>you can access files larger than 4 GB and sizeof(some_long) is 8.
>> And is the 64 bit Linux now all 64 bit??
>Just about. Currently, the filesystem does not support files larger
>than 4 GB. Work is underway to upgrade that, if it is not upgraded
>already in the experimental 2.1.xx kernels.
>Note that you need the DEC Alpha CPU for 64-bit Linux.
I think I might make an exception interrupt here. The Cyrix 6x86
is capable of both 32 and 64bit operations thanks to the fact that it
has a dual pipeline that is interlocking. Each pipe (X&Y)on the Cyrix
6x86 is 32bits wide. When interlocked, they become one 64bit word
that the Cyrix 6x86, afaik (probably need to research this more), can
access and address in 64bit form.
The Cyrix 6x86, again, afaik, can define a 64bit far pointer if
the assembly programmer so desires using this interlock process,
though I'm not sure what pc desktop (generic term) needs to address a
1.85x10^19 hard drive address (2^64) or memory reference at this point
in time other than possibly a Cray. A Pentium wouldn't know what to
do with it and would probably choke...either that or crash and burn
[what a pleasant and interesting image...a PentiumPro slowly
smoldering into ash after attempting to access a 64bit far
pointer...brings a smile to this wizened face...ah, the smell of
burning silicon ;-)]
If this is an accurate deduction, then it would be an easy thing
to say that where Pentium is a 16/32bit machine, Cyrix 6x86 is a
32/64bit machine. If indeed this is the case, then there is already a
processor available (at a fraction of the cost of a DEC Alpha CPU)
that is capable of handling 64bit operations, the Cyrix 6x86.
Nothing real can be threatened.
Nothing unreal exists.