split up x862-aset2 #495
Merged
split up x862-aset2 #495
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
One case deals with the write barrier, and the other with all others. In the write barrier case, we need to get vector/index/new-value into arg_x/arg_y/arg_z; te other cases have more flexibility. (We already do this on the ARM.)
We can do this now because the needs-memoization case has been moved to x862-aset-via-gvset.
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.
Following a similar split on the ARM port (see 1257acd), split
x862-aset2 into two cases, one which handles the needs-memoization
case, and another that handles the other cases.