On Wed, 13 Feb 2002, Peter Epstein wrote: > The key is to profile your application to find the bottlenecks. Look for > bits of code that do a lot of heavy computation with as few OS calls as > possible. These are your candidates for porting to ARM native code. Of > course, optimizing your code without reverting to ARM native code is also a > valuable alternative.
also, dont doubt the m68k emulator :) it is fast :P if your rewriting API's, especially graphical ones *g* - your m68k code emulated runs faster than native ARM :) thats the results of our tests anyhow :) you should also be aware of the overhead involved in switching to ARM mode to run the native code, if any. optimization is a tricky thing :P circumstances are very important. // az [EMAIL PROTECTED] http://www.ardiri.com/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
