Implement get_gc_trigger() for LockFreeImmortalSpace #1003
Merged
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 PR fixes two issues in
LockFreeImmortalSpace
and adds a test.get_gc_trigger()
. AsLockFreeImmortalSpace
does not haveCommonSpace
, we cannot use the default implementation.HeapMeta
, so the address range ofLockFreeImmortalSpace
won't clash with other spaces. This closes LockFreeImmortalSpace should not assume it can use the whole heap range #314.