[PATCH] Entangle the C Program Heap initialization

Sebastian Huber sebastian.huber at embedded-brains.de
Thu Oct 1 16:04:40 UTC 2020

On 01/10/2020 17:51, Gedare Bloom wrote:

> On Thu, Oct 1, 2020 at 9:45 AM Joel Sherrill<joel at rtems.org>  wrote:
>> On Thu, Oct 1, 2020 at 10:07 AM Gedare Bloom<gedare at rtems.org>  wrote:
>>> This looks ok to me. I suppose eliminating the dependency requires the
>>> function pointer indirection. The only thing I don't see is why
>>> redefinition of the _Workspace_Malloc_initializer is allowed in both
>>> wkspacemallocinitdefault.c and in confdefs/wkspace.h. I would think
>>> that will cause an error for multiple definitions.
>> I think Entangle is the wrong work. Disentangle or possibly decouple.
>> Does minimum actually reflect what you think is the smallest possible
>> configuration now? That as always the test's purpose -- to have a single
>> executable that was the smallest we thought we could produce. It seems
>> with all your changes that it needs a review for tweaks to the configuration.
> Should open a ticket to review this. Certainly after all the static
> initialization/construct stuff it should be possible to go smaller.
I am not done with the initialization and workspace changes, but it is 
not much left to do.

More information about the devel mailing list