Unused Fragments

EdWaugh · Joined: 07 Dec 2004 Posts: 127 Location: Southampton, UK

Hi all,

I'm sorry if this has been asked before, I did a search but it returns over 1300 matches.

I'm trying to eek the last few bytes of ROM from my device and I was curious about the following in the sta file:

ROM used: 124410 (95%)
130916 (100%) including unused fragments

I guess the fragments are small gaps across blocks in the flash? Is there anyway to optimise this better? 5 % of 131 kB is 6.5 kB!

Cheers

Ed

Ttelmah · Joined: 11 Mar 2010 Posts: 19539

Bit of a 'roundabouts and swings' thing.
Splitting routines into smaller sections, will give the compiler some smaller bits to 'play with', and may allow it to optimise better, _but_ may increase the total size, as calling a routine adds overhead.
Generally, look instead at whether there are things you can do to decrease the total code size. Code 'drinkers', are arithmetic, printf etc.. If (for instance) you are doing a sum completely in fp arithmetic, but part of it is multiplication, and only involves integers, you may be able to save some significant space by forcing the use of integer arithmetic for this part. On printf, look for 'repeated' statements. If you use a printf, to the same target, with the same format specifier in multiple places in the code, make this into a separate routine, and call this routine, rather than having the multiple printf's. Generally I'd not be at all surprised if you couldn't save at least 25%, by moves like this, and this will also reduce the size of the routines involved, allowing more efficient packing at the same time....

Best Wishes

EdWaugh · Joined: 07 Dec 2004 Posts: 127 Location: Southampton, UK

Hi Ttelmah,

Thanks for your response. I have had a look at the fp in my code already but I may have another go, I'm curious about the printf stuff tho, surely this is just a single function call that decodes the format string at run time? Otherwise am I able to see all the separate calls in the tree/statistics?

Thanks

Ed

EdWaugh · Joined: 07 Dec 2004 Posts: 127 Location: Southampton, UK

Hi again,

I had a look at the use my program is making of anything called pstring or printf:

Ttelmah · Joined: 11 Mar 2010 Posts: 19539

printf, is not a 'single function call'. It is decoded at _compile_ time, for the specified options, and 90% of the time coded inline. The parts visible in the symbol tree are internal subroutines this then calls. If you search through the .lst file, for the lines coding printf, don't be surprised is there are 70 to 80 bytes setup for every one of the calls....

Best Wishes