Op 03/03/2017 om 02:29 PM schreef David W. Schultz:
> On 03/03/2017 05:20 AM, Bob von Knobloch wrote:
>> As far as I can see, the 'bloat' is in library funcs (newlib?).
>> Why the 50% increase and can I mitigate this somehow?
>> Regards,
>> Bob von Knobloch.
> Hard to say without seeing the code. Have you looked at the resulting
> file using objdump? If not, that can disassemble the code into something
> readable so you can see just what is going on.
An easier approach is to let the linker generate a map file and compare 
between the two compilers. The mapfile shows the size of each object 
(source file and imported library functions). It can be code generation 
is less efficient or libraries are bigger. The original MSP430GCC C 
libraries are very compact so it wouldn't surprise me if it turns out a 
different library is the cullprit.

N. Coesel

Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Mspgcc-users mailing list

Reply via email to