[avr-libc-dev] -O3 is bad

[Joerg Wunsch]

-O3 is quite often a pessimization in our case.  It causes a good deal
of code bloat, and although i didn't measure any possible speed
improvement, i guess there won't be much if any.  Is there any
particular reason for chosing it for the avr4/avr5 architectures?

With -O3, vfprintf() compiles into > 1300 bytes on avr5, while with
-O1 -mcall-prologues -mno-tablejump, it's about 1100 bytes.

-- 
J"org Wunsch                                           Unix support engineer
address@hidden        http://www.interface-systems.de/~j/