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
The avr-libc malloc and friends such as realloc and free are implemented in a
way that is not re-entrant.
When using FreeRTOS, any application code can be pre-empted and needs to be
thread-safe. FreeRTOS does have its own allocators independent of avr-libc,
and one allocator which wraps
As Taavo Raykoff wrote:
> Is there any active maintainer on avr-libc?
Depends on your definition of "active".
I am the maintainer of it, but unfortunately, even though my activity
is very low (being busy in many respects, family, job, German amateur
radio league, other opensource stuff as
Is there any active maintainer on avr-libc? I’d like to push a fix upstream.
Thanks,
Taavo
___
AVR-libc-dev mailing list
AVR-libc-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
