WIP: Add RefScanPolicy to object-scanning methods of Scanning #1437
Conversation
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
The VM binding only needs to know the `RefScanPolicy` trait but not its implementations.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We use the
RefScanPolicytype to tell the object-scanning methods what to do with strong and weak reference fields, respectively, and whether they should "discover" weak reference fields (or objects that contain them) in VM-specific ways if the VM chooses to discover weak fields during tracing (instead of pre-registering all such fields (or objects that contain them) upon construction).This PR is intended to pave a path for porting the OpenJDK-style reference processing from the
lxrbranch and eventually supporting LXR.TODO:
lxrbranch.RefScanPolicyimplementation for barriers.Fixes: #1376