[avr-gcc-list] avr-gcc runtime lib, avr-libc, and multi-thread

[Kang Tin LAI]

Hi,

I want to switch to the lib functions in avr-libc from my own, since malloc in 
avr-libc, for example, is better than mine, and other such as stdio functions 
are here and ready for use. But the avr-libc is lake of common resource locking 
facility.

In avr-libc:

#define MALLOC  123
void *malloc(size_t n){

        lock(MALLOC);   /* add a common resource access control */
        /* do malloc */
        unlock(MALLOC); /* add a common resource access control */
        return p;
}

In simple kernel, lock() and unlock() may be just a simple interrupt disable and 
enable operation, for sophisticate kernel, it may be a spin lock and spin unlock 
mechanism. Whatever, keep the changes as little as possible, any comment?

For avr-gcc runtime lib, is there any special or need to take care for 
multi-tasking? I use avr-gcc for compiling my kernel since day one and found 
nothing wrong, so avr-gcc runtime should be re-enter-able and multi-thread safe, 
is it?

--
---
Kang Tin LAI <address@hidden>
-----