-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement movsq #40
Implement movsq #40
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I havent reviewed it properly, but we should be able to have one movsX function to do all movs, movsb, movsw... etc. we also should be able to get the size info from operands. That would be a more elegant solution
I think maybe we have to pass a size paramater into that movsX? |
I am not exactly sure, but operands[1].size should give us the correct size, so we dont really need to pass a parameter. |
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
thank you for your contribution |
Implement movsq I encountered in sprotect