Re: [PATCH] Nano-malloc: Fix for unwanted external heap fragmentation
Ola Olsson <[email protected]>
| Newsgroups | gmane.comp.lib.newlib |
|---|---|
| Message-ID | <CABAco3Aws8KbT7mn5g3qtiViquKy_LcMZHhupfkdhvGfqwsCTA@mail.gmail.com> |
+Corinna > If someone wants to work on your patches in newlib, that's fine; they're >definitely an improvement over the current code. My work is focused on > picolibc, and when I have some time, I try to get fixes merged into >newlib. Sorry Keith, English is not my native language and I don't know who to contact in this newlib project. I guess that someone is Corinna? Corinna, sorry for the long discussion. Keith has a superior nano-malloc in his picolibc and I totally support it to be backported once he is ready. Until then, I would like to get this patch merged if possible since it could benefit us right now. Also, it can be used later for comparison if (unlikely though) something goes haywire with that integration. That's my two cents. >Oh, I should have linked the blog post I wrote about this a while ago: > https://keithp.com/blogs/picolibc-news/ > There's a long section on the nano malloc changes. Keith. Thanks for the explanations regarding the API robustness and this blog post. It's brilliant. Well written and nicely explained.