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

CVTSS2SI use wrong operand types #31

Closed
Kashio opened this issue Dec 24, 2022 · 2 comments
Closed

CVTSS2SI use wrong operand types #31

Kashio opened this issue Dec 24, 2022 · 2 comments

Comments

@Kashio
Copy link

Kashio commented Dec 24, 2022

Right now CVTSS2SI encoded with opcode F3 0F 2D use operand type ss for its operand of addressing W which is defined as:

Scalar element of a 128-bit packed single-precision floating data.

According to the intel docs:

Converts a single-precision floating-point value in the source operand (the second operand) to a signed double-word integer (or signed quadword integer if operand size is 64 bits) in the destination operand (the first operand). The source operand can be an XMM register or a memory location. The destination operand is a general-purpose register. When the source operand is an XMM register, the single-precision floating-point value is contained in the low doubleword of the register.

Since it's only copying the lower 32 bits of the register and the memory variant is also referencing 32 bit memory the operand type should be of type d which is defined as:

Doubleworld, regardless of operand-size attribute.

Kashio added a commit to Kashio/x86reference that referenced this issue Dec 24, 2022
@BarebitOpenSource
Copy link
Contributor

This one looks right. Refer to #23.

@BarebitOpenSource
Copy link
Contributor

Feel free to reopen this issue if you still think the operand type is wrong.

@BarebitOpenSource BarebitOpenSource closed this as not planned Won't fix, can't repro, duplicate, stale Jan 31, 2024
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

No branches or pull requests

2 participants