David Linker writes:
> Add -O1flag
> 39,272 bytes
>
> Add -O2 flag
> 39,844 bytes
>
> It looks like the -O1 and COMPRESS options get it within "striking
> distance".
Try using -Os ("optimize for size"). It's usually faster than -O1 and
smaller than both -O1 and -O2.
--
Greg Parker [EM
Thank you to all who replied.
Here are the results:
Original CW PRC
38,538 bytes
PRC-Tools with no compiler flags, COMPRESS for bitmaps
47,228 bytes
Add -fno-exceptions -fno-rtti flags
No change (not surprising since I am using straight C code)
Add -O1flag
39,272 bytes
Add -O2 flag
39,844 by
When you compile for release, you want to add
ADDITIONAL_COMPILER_FLAGS = -O2
to your makefile. But don't do this when compiling for debug, only just before
final testing for release. For debug, you actually want code that matches your
source line-for-line, and optimization can destroy that.
Of David Linker
> Sent: Wednesday, May 18, 2005 10:33 AM
> To: Palm Developer Forum
> Subject: Code bloat with PRC-Tools?
>
> I have just migrated an application from CW to PRC-Tools. My
> completed application was 38K with CW, but it is 51K with PRC-Tools!
>
> If I add "
[EMAIL PROTECTED] On Behalf Of David Linker
Sent: Wednesday, May 18, 2005 10:33 AM
To: Palm Developer Forum
Subject: Code bloat with PRC-Tools?
I have just migrated an application from CW to PRC-Tools. My
completed application was 38K with CW, but it is 51K with PRC-Tools!
If I add "COMPRES
I have just migrated an application from CW to PRC-Tools. My
completed application was 38K with CW, but it is 51K with PRC-Tools!
If I add "COMPRESS" for the bitmaps, it is still 48K.
Are there some options I should be setting for smaller code size? I
looked in the documentation for m68k-pa
