From Newsgroup: comp.sys.mac.system
Does anybody know how Apple has solved the endianness problem in
Rosetta?
<
http://en.wikipedia.org/wiki/Endianness>
Because the G4 processor can be used as both a big-endian and a
little-endian processor, and the G5 only as a big-endian, VirtualPC
emulating the little-ending Intel-processor runs slower on the G5 than
on the G4.
But this should mean that Rosetta running non-Universal MacOS X programs
would have to emulate big-endianness on a little-endian processor -
giving the same problems as known from VirtualPC 7 on G5.
When I google on it I see that some people think that the MacOS X API
calls are done natively, and that this should make the differenc. But
does anybody know how Rosetta works?
--
Per Erik Rønne
http://www.RQNNE.dk
--- Synchronet 3.18b-Win32 NewsLink 1.113