Joerg Wunsch wrote:
As Russell Shaw wrote:
If you need stdio functions that call malloc, hmm, I think that'll
put something else onto your list of non-reentrant functions ;-),
but still, you could just import the implementations for
malloc/free into your own application, and make them thread-sa
As Russell Shaw wrote:
> >If you need stdio functions that call malloc, hmm, I think that'll
> >put something else onto your list of non-reentrant functions ;-),
> >but still, you could just import the implementations for
> >malloc/free into your own application, and make them thread-safe.
> What
As Anatoly Sokolov wrote:
> In new ATMega devices EEPROM support registers are located to other
> addresses than in AT90S/old ATMega/ ATTiny, it does illogical and
> error prone the generalized definition of these registers in IO.h.
These registers have once already been defined in each individua
Joerg Wunsch wrote:
As Branislav Katreniak wrote:
I want to use a multitasking OS in my project. What is the best way
to encapsulate all calls to malloc() and free() with a
synchronization primitives? I want all calls to these functions
(even from other libc functions) to be reentrant safe and
Hello.
In new ATMega devices EEPROM support registers are located to other
addresses than in AT90S/old ATMega/ ATTiny, it does illogical and error
prone the generalized definition of these registers in IO.h. I suggest to
change the order of definition EEPROM registers as follows:
1.To define
As E. Weddington wrote:
> >A very rousing: me too!! :-)
> Oh, Jörg, should we mention this both the in the NEWS file as well
> as a News item in the avr-libc project on Savannah?
I'm not so sure about the NEWS file, I merely thought of it as kind of
release notes, so with boring technical detail
