> -Original Message-
> From:
> [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> org] On Behalf Of Bernard Fouché
> Sent: Friday, July 04, 2008 8:54 AM
> To: Wouter van Gulik
> Cc: avr-libc-dev@nongnu.org
> Subject: Re: [avr-libc-dev] Definition of putchar/ge
Bernard Fouché wrote:
IMHO the 'stock' distribution of avr-gcc/avr-libc should be tuned to
give results as good (hence small) as possible with -Os since most of
the traffic in the mailing lists seems code size oriented, so I have a
point of view similar to Wouter.
I'm with you on this one, an
Bernard Fouché schrieb:
Or have conditional compilation of headers according to the
optimization required, (so in Wouter's case putchar() would be kept as
a function call with -Os, but replaced with fputc() with -O2/3),
however I dunno if there is a macro or something already defined
allowi
Hi.
I just began yesterday to move from gcc-4.2.0/avr-libc-1.4.6 to
gcc-4.3.0/avr-libc-1.6.2 (with the patches taken from WINAVR0610).
I first experienced a significant code growth (about 4%) because of:
- functions like eeprom_read/write_byte() that now inline more code,
hence I had to writ
