Re: [avr-libc-dev] Is there any active maintainer?

[Joerg Wunsch]

As Taavo Raykoff wrote:

> What is the route to becoming an allowed committer — if I or someone
> has time to help out with this?

Given the low activity of all existing committers (including me), I'd
say: enough dedication ...

Regarding your malloc stuff: there is a testsuite in the source
repository, glued around simulavr.  It contains a number of regression
tests to make sure no older malloc bug has been re-introduced.  It
would be really cool if you could see whether you can get that
testsuite to some life, and to test your patch.

Otherwise, I love the idea of allowing malloc() to become reentrant.

Another idea would be moving the existing malloc into a malloc_r()
implementation, with standard malloc() wrapping around it.  That's
basically what newlib does for ARM-GCC.

-- 
cheers, Joerg               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)