Flesh out API for malloc with buffered finalization #14
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
This introduces a new malloc function `GC_buffered_finalize_malloc` which ensures that unreachable objects are added to a 4KiB thread-local buffer to be later finalized. Once the buffer is full, it's passed to a user supplied closure. The disclaim API in Boehm has no mechanism for detecting which allocations in a free-list are simply empty and which require finalizing. So in order to get around this we change mark procedure, using an extra bit in the object header to determine whether or not an object has a finalization closure.
|
Closing based on offline discussion |
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.
This introduces a new malloc function
GC_buffered_finalize_mallocwhich ensures that unreachable objects are added to a 4KiB thread-local buffer to be later finalized. Once the buffer is full, it's passed to a user supplied closure.The disclaim API in Boehm has no mechanism for detecting which allocations in a free-list are simply empty and which require finalizing. So in order to get around this we change mark procedure, using an extra bit in the object header to determine whether or not an object has a finalization closure.