User-defined allocator - COROUTINE_MALLOC, COROUTINE_REALLOC, COROUTINE_FREE #8
+687
−9
Conversation
This file contains 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
|
Since d4ab4a2 allocating the memory for stack requires platform dependent OS API calls with special flags to ensure optimal memory settings for the stack. So for each platform we are going to hardcode some thing specific. For the rest of the data structure allocation I think using realloc from libc is fine. |
Sign up for free
to 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.
Hello!
This pull request implements COROUTINE_MALLOC, COROUTINE_REALLOC, COROUTINE_FREE macros that allow the user to define their own allocator. I've also included a modified version of "counter.c" example and a simple testing allocator "myalloc.c" just to show how one can use a custom allocator with the coroutines library.
Have a nice day!