Hi !
Samedi 10 F�vrier 2001 11:52, Aaron Ardiri a �crit:
> keep in mind.. if you do this type of code, then CHECK the CPU before
> you do so.. this optimized code can be emulated on an ARM machine,
> however - it worked best on a m68k :)
There is something I don't understand, here : no matter how work the ARM
processor, little endian or big endian, if you do ( or emulate ) a
MOVEM MEM REGS then a MOVEM REGS MEM,
you should finally obtain the correct result, am I wrong ?
Except if the MOVEM MEM REGS instructions read from mem and store the values
in the registers in one order ( let's say little indian ) and the instruction
MOVEM REGS MEM read from register and store in mem the values in an other
order, but this will be a bug, not a feature ! :-)
Anyway, I agree : even if the emulated code was working, I suppose than the
WinCopyRectangle of the API ( written directly in ARM, I hope... ) should be
much more faster than the emulated 68K code, even optimized.
Just a question : when calling the FtrGet function ( with
sysFtrNumProcessorID ), does it return a specific value, or does it emulate a
DragonBall processor too ??
:-)
--
Daniel Morais
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
