Fix using R8-15 in addressing #7
Open
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
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.
REX registers were previously not allowed in memory addressing operands (i.e., Operand::Indirect*).
To be honest, I'm not too experienced in x86 opcode encoding and I'm not to sure if this is the correct way to fix this, but it "works for me" (for now).
For example, I'm not sure if this change should be extended to
encode_indirect_32usingReg::R8Detc., as it seems to be used as a fallback whenencode_indirect_64fails.Feel free to comment on my concerns and make suggestions for further modifications.