Hi.

Did you try with:

-finline-limit=10
-fno-if-conversion
-mcall-prologues

I ran into similar problems with code size and these options made the code fit in a bootloader area (however my bootloader is much bigger thant 512 bytes)

I've also seen that EEPROM related function calls were inlined each time, so I wrote a couple of wrapper functions to avoid this inlining.

 Bernard

DLC wrote:
I've noticed that too. My Arduino bootloader fits into the 512 byte boot section when compiled with avr-gcc 3.4, but doesn't when compiled with avr-gcc 4.3.

You've found an even closer gap with the jump between 4.1 and 4.3.

DLC




_______________________________________________
AVR-GCC-list mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list

Reply via email to