Re: [avr-gcc-list] Re: [avr-libc-dev] Please have a look at avr-libc patch #3750

[Bernard Fouche]

Joerg Wunsch wrote:

> Errm, you'd still need to supply a dummy implementation for malloc()
> anyway when using the floating-point versions.  vfprintf() or
> vfscanf() will cause reference to malloc() [and free()] as they do not
> know at link-time they won't really be needed.
>
>  
Now why not have an alloca(3) in libc? Sure it is not the best way to manage
dynamic memory but vfprintf/scanf are typicall applications where it
is acceptable. And a functionning alloca() is always handy.

Bernard