Opened on 12/09/19 at 09:09:11
Last modified on 11/10/22 at 09:58:49
#3835 closed enhancement
Support statically allocated threads — at Initial Version
Reported by: | Sebastian Huber | Owned by: | Sebastian Huber |
---|---|---|---|
Priority: | normal | Milestone: | 5.1 |
Component: | score | Version: | 5 |
Severity: | normal | Keywords: | qualification |
Cc: | Blocked By: | ||
Blocking: |
Description
In some applications it is desirable to have statically allocated resources for all operating system objects.
In addition to the thread control block, up to four memory areas are currently allocated by a thread:
- stack area
- TLS area
- FP context
- thread queue heads
Currently the FP context and the TLS area are separately allocated from the workspace. This complicates the workspace size estimate. Add the FP context and TLS size to the stack size and place them in the stack area. This makes it also possible to move the stack area allocation out of _Thread_Initialize(). Use a hook to get the thread queue heads which is configured depending on the unlimited objects option of the configuration.