> Ok, so I must understand that there is no categoric "32 bit operations are > quicker" on Palm. If I were on a PC, I would choose the 32 bit variant > categorically, because of the 32 bit architecture. So the best solution is > to "test and see" on the device...
Actually, you would not necessarily be right to choose 32 bit variant categorically on the PC. What about the differences between different versions of the x86 architecture? What about the AMD64 chipset? Or the IA64 chipset? Etc -- even on the PC the answer is not categorically clear. Just like on the Palms as Ron described. Also remember that OS 5.0 devices are ARM not 68k, and the 68k code runs in an emulation layer. Your question is a good one, but the answer is multi-faceted. So yeah, you really do need to try it out on different devices. > > Many thanks! > Dan Patrutiu > > > "Ron Nicholson" <[EMAIL PROTECTED]> wrote in message > news:109782@palm-dev-forum... > > > > You can always compile the C code using various levels of optimization, > > then look up the instruction cycle timings for each instruction in > > the Motorola MC68000 manual (available on their web site), and > > add up all the cycles. > > > > However, different Palm models have different numbers of > > memory wait states, so you also add those cycles. If the display is > > in shared memory, then you'll also need to add the cycle penalty > > caused by memory competition. With armlets, you'll also need > > to take into account cache hit/miss ratios and penalties. > > > > At some point, there are so many variables that it become easier > > to get the right answer by running tests on the actual hardware. > > > > Ron Nicholson > > HotPaw > > <http://www.hotpaw.com/rhn/hotpaw> > > > > > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
