[Feature] Support pvPortRealloc #1315 #1350
Open
+497
−0
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.



Description
This PR introduces a new API
pvPortReallocto FreeRTOS, providing dynamic memory reallocation similar to the standard C library'srealloc. WithconfigSUPPORT_HEAD_REALLOCenabled, applications can now resize heap-allocated memory blocks at runtime, either shrinking, expanding in place, or reallocating with data migration when needed.Key Changes:
pvPortReallocAPI inportable/MemMang/heap_4.candheap_5.c.configSUPPORT_HEAD_REALLOC(default 0, must be 1 to enable realloc support).FreeRTOSConfig.hand checked for correct configuration use.malloc.free.Test Steps
configSUPPORT_HEAD_REALLOCand ensure dynamic allocation is also enabled.heap_4.corheap_5.c.pvPortReallocto:NULLas input.0.Checklist:
Related Issue
#1315
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.