Coda schrieb:
Ach so: Wie war das nochmal mit dem 32-bit-Kernel in Tiger?
"For most developers, 64-bit functionality in Mac OS X version 10.4 will have no impact on them. Most device drivers do not need to change [...]
Because 64-bit applications will be supported using a 32-bit kernel, this 64-bit support will have no impact on most device driver or kernel extension writers. However, there are exceptions, as explained in “Device Driver Issues”."
"- Myth #2:
Myth: The kernel needs to be 64 bit in order to be fully G5-optimized.
Fact: The kernel never needs to directly address more than 4 GB of RAM at once. The kernel is able to make larger amounts of memory available to applications by simply using long long data types to keep track of mappings internally."
Zum Thema "Die Koexistenz von 32 und 64-bit ist bei x86 und PowerPC in allen wesentlichen Zügen identisch gelöst.":
"Myth #1:
Myth: My application has to be 64-bit (or run on a G5) to use 64-bit data or do 64-bit math.
Fact: 32-bit applications already have the long long data type, which is 64 bits."
"Myth #5:
Myth: My application will have much faster performance if it is a “native” 64-bit application.
Fact: This is true for some other architectures because the number of registers and the width of registers changes between 32-bit and 64-bit mode. However, the PowerPC architecture does not have either of these limitations. It was designed for 64-bit computing from the beginning, and supports 64-bit arithmetic instructions in 32-bit mode. Thus, on PowerPC architectures, software does not generally become faster (and may actually slow down) when compiled as a 64-bit executable."
Mit "some other architectures" ist hier wohl der x86 gemeint.