This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: Confusion about possibly unsafe malloc_r?
Now I'm really confused.
I'm working with newlib version 2.5 as distributed in the GNU ARM Toolchain.
I implemented everything I could find in the documentation.
Is the following correct and complete WRT newlib 2.5.0 ???
http://www.nadler.com/embedded/draft1_newlibAndFreeRTOS.html
Thanks,
Best Regards, Dave
PS: Kudos for pushing C++; we've been doing so for a couple decades.
But FreeRTOS has a lot of advantages and required by some of our customers,
and works fine for C++ (though I've added some ctor/dtor wrappers
to ensure symmetric acquisition/release of interrupts, locks,
semaphores, etc.).
On 6/27/2017 2:26 PM, Freddie Chopin wrote:
On Sun, 2017-06-25 at 10:22 -0400, Dave Nadler wrote:
Could you point me at documentation (or sources) explaining how
to implement "retargetable locks"?
"Retargetable locks" are a new feature, introduced at the beginning of
this year. You can see an example implementation in my C++ RTOS here:
https://github.com/DISTORTEC/distortos/blob/master/source/newlib/locking.cpp
Regards,
FCh
--
Dave Nadler, USA East Coast voice (978) 263-0097, drn@nadler.com, Skype
Dave.Nadler1