----- Am 3. Feb 2020 um 7:10 schrieb Chris Johns chr...@rtems.org:
> On 3/2/20 4:27 pm, Sebastian Huber wrote:
>> ----- Am 3. Feb 2020 um 0:01 schrieb Chris Johns chr...@rtems.org:
>>
>>> On 3/2/20 12:28 am, Sebastian Huber wrote:
[...]
>>> I am not sure what the "demand" is and where it is coming from.
>>
>> Currently, the workspace and C program heap area always initialized. With
>> this
>> patch, they are only initialized if they are used. So, a future application
>> which only uses statically allocated resources, will not have the heap
>> handler
>> in its executable.
>
> Is the reason why and approach for making a fully static application
> documented
> anywhere? How will a user know this exists?
I work on this for a couple of years. It is a series of lots of small steps.
The first major step was the introduction of self-contained synchronization
objects in Newlib in 2015. Once it is done it should be documented the Classic
API Guide maybe under Key Concepts.
>
> I assume this helps low memory targets?
Yes, it helps low memory targets, debugging, and applications which don't need
dynamic memory at all.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
