Uh oh!
There was an error while loading. Please reload this page.
Prepare Strata v0.1.1 memory policy foundation - #16
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Strata::MemoryPolicyas the shared ZekStack configuration vocabulary for general allocations and task stacksPlacement::Defaultsemantics distinct from inheritance and document safety-precedence rulesMutexandRecursiveMutexowners using static FreeRTOS creation with internal Strata-backed control storageFreeRTOSMutexexample0.1.1Validation
Branch push CI for commit
bc184dcfded6a32f4cce7d06b7a39147456a44ec:Compatibility
This is additive to the v0.1.0 placement/failure contract.
Strata.hgains only the platform-neutralMemoryPolicytype; FreeRTOS mutex integration remains behind<strata/freertos/Mutex.h>. There is no global memory configuration, and existingTaskConfig/QueueConfigsemantics are unchanged.