If you like to stay with gcc, you should look out for peal. It will
allow you to spread your ARM-code over several 64k-resources (which
isn't complicated at all :-). But also will give you global vars in your
pnolet.
1: no, not really
2: no, sectioning isn't necessary. pnolet can be very large and jumps
are 32-bit. You just would spilt the large ARM binary into small chunks
and put them together on the device. Maybe peal can do it even smarter
with calls between the different resource ptrs.
3: no globals for example, if you don't use peal.
Regards
Henk
David Ghandehari wrote:
Hi again, folks,
So, I noticed that prc-tools comes with an arm-palmos compiler as well
as the expected m68k-palmos. I have a large multi-section C++ 68k
application, and I'd really like to just compile the whole thing into
ARM and just have a 68k stub that checks to see if the platform supports
ARM and then launches the ARM version, otherwise continuing with the 68k
portion. I haven't done anything with ARM yet other than try and read up
what I can scrounge up, so I am a bit clueless and scared here.
so:
1. Is compiling an entire app to ARM feasible? Is there any reason I
wouldn't want to do this?
2. If my ARM code ends up being greater than 64k (which it will), how
does having multiple ARM code resources work? Do I need to do the same
thing in terms of sectioning out code?
3. Are here any other considerations I should be considering regarding
ARMifying my project?
Thanks,
-DG
--
-------------------------------------------------------------------------
Henk Jonas [EMAIL PROTECTED]
Palm OS ® certified developer
Please contact me, if you need an off-site contract worker.
-------------------------------------------------------------------------
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
