-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
JIT: Emulate missing x86 shift instructions for xplat intrinsics #111108
Merged
+78
−27
Merged
Changes from 7 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
41f4460
emulate missing x86 shift instructions
saucecontrol 478732d
disable vpsraq emulation on 32-bit
saucecontrol 5f4ad0f
use logical shift for mask
saucecontrol 85ba0bb
fix disasm for shift instructions
saucecontrol 19946a1
allow vpsraq emulation on 32-bit for const shift amount
saucecontrol 59e9216
Merge branch 'main' into xplat-intrinsics
tannergooding b76fe4e
Merge branch 'main' into xplat-intrinsics
tannergooding 5849012
review feedback
saucecontrol File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
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.
Not quite sure this is the "best" fix.
This feels like a case where we could utilize the existing tags for memory operand size for the register as well rather than hardcoding a one-off special case.
Not going to block on it, especially since this is only used for disassembly; but its something that would be nice to have improved for this and other cases where the last operand is a different register size than the others.
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.
Can you elaborate on your preferred fix here? This is already using the tuple type rather than hard-coded instruction list -- I just mention shift in the comment explicitly because it's the only thing I'm aware of that uses full xmm/m128 for what is ultimately an 8-bit scalar, and this should be the only encoding form where that xmm fix is required.