Mike allegedly writes:
If I do embedded programming for a micro, my compiler goes from C to assembly as there is no OS running on the micro... But you're saying that CW does not produce op codes for the specific hardware platform
If you are using CW v8, that could be correct. CW for PalmOS v8 produces 68k op codes, whether or not the native hardware ISA is a PowerPC (using the Mac version of the POSE emulator), x86/IA32 (using the Windows or linux version of POSE ), ARM (using PACE on an m550 or an NX60). Or the hardware platform could have an actual 68000 CPU (DragonBall EZ on a Palm Vx, etc.)
The compiler doesn't know whether the op codes will be executed in hardware, emulated, or simulated on a (or perhaps layers of) virtual machine. The OS traps are just calls to another program; your application doesn't know whether that other program consists of mostly ARM, x86, Java byte-codes, or 68k machine code. On an m550, they'll run fastest if they're ARM 7T instructions, so I assume that's how the OS is done.
What are they referring to that is native then ...
Some of the stuff on a Palm OS 5 handheld is actually in ARM ISA machine code. You can compile these using tools such as arm-elf-gcc, or the CW v9 armlet compiler. 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/
