-
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
Take the memory operand size for some hw intrinsic instructions #57603
Conversation
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsFor certain HW intrinsic instructions like insert/extract, during outputting, we should check the memory operand size rather than the data operand size to determine if the memory is correctly aligned. We already have special handling during I tried searching around Fixes: #57458
|
Failures are related to #57620 |
@dotnet/jit-contrib @tannergooding |
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.
I'm not sure if we've exhaustively checked instructions for places where the attr
size and the memory size
can differ. The display handling was best effort based on known issues, afair.
5d3c870
to
46cb9f3
Compare
Hello @kunalspathak! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
For certain HW intrinsic instructions like insert/extract, during outputting, we should check the memory operand size rather than the data operand size to determine if the memory is correctly aligned. We already have special handling during
emitDispIns()
but should be done also during outputting.I tried searching around
id->idOpSize()
for other places this must be happening and don't see anything except at the code path I updated. While I was there, also pass precalculatedsimdSize
value instead of recalculating it again.Fixes: #57458