Skip to content
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

Fix operand types for vpand #177

Merged
merged 1 commit into from Sep 19, 2016

Conversation

BlairArchibald
Copy link

The intel developer manual specifies vpand as having operands "xmm1 xmm2
xmm3/m128". This change reflects this in dyninst.

The intel developer manual specifies vpand as having operands "xmm1 xmm2
xmm3/m128". This change reflects this in dyninst.
@jdetter
Copy link
Contributor

jdetter commented Sep 12, 2016

@wrwilliams This is good to go, this is a small correction and it shouldn't cause any issues.

@wrwilliams
Copy link
Member

Are there other similar cases in this section of the tables, or was this a lone wolf?

@BlairArchibald
Copy link
Author

I had a quick look and didn't see anything immediately obvious, although I'm not an x86 expert by any means.

@wrwilliams
Copy link
Member

Approved for 9.2.1. We should write up a test that generates a bunch of random bytes and verifies no assertions and all operands are used.

@jdetter
Copy link
Contributor

jdetter commented Sep 13, 2016

@wrwilliams Sorry I forgot to get back to you on this. I remember I had to add this instruction by hand and it was just a simple typo. There shouldn't be any other issues related to this one.

@wrwilliams wrwilliams merged commit aa632d9 into dyninst:v9.2_patches Sep 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants