-
Notifications
You must be signed in to change notification settings - Fork 1.7k
x64: Ensure that constants are always 16 bytes for XmmMem #4790
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
Merged
elliottt
merged 6 commits into
bytecodealliance:main
from
elliottt:trevor/xmm-mem-alignment-bug
Aug 26, 2022
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
f51a6ba
Add a regression test
elliottt 922957e
Ensure that mem cases for XmmMem are always to 16-byte values
elliottt cf62494
Accept a u128 argument instead
elliottt 80e1073
Reuse logic from put_in_xmm_mem in put_in_xmm_mem_imm
elliottt cc3db22
Use `copied` instead of `cloned`
elliottt baad83c
Refactor constant construction for u128
elliottt 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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
17 changes: 17 additions & 0 deletions
17
cranelift/filetests/filetests/runtests/x64-xmm-mem-align-bug.clif
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| test run | ||
| set enable_llvm_abi_extensions | ||
| target x86_64 | ||
|
|
||
| ; Regression test for unaligned loads to xmm registers when relying on automatic | ||
| ; conversion to XmmMem arguments in ISLE. | ||
| ; https://github.com/bytecodealliance/wasmtime/issues/4761 | ||
| function %a() -> f64 { | ||
| ss0 = explicit_slot 59 | ||
|
|
||
| block0: | ||
| v0 = f64const 0x1.d7d7d7d7d006fp984 | ||
| v1 = fcopysign v0, v0 | ||
| return v1 | ||
| } | ||
|
|
||
| ; run: %a() == 0x1.d7d7d7d7d006fp984 | ||
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.
Should we just run this on all architectures as well as the interpreter? The bug was x64-specific but the test should work everywhere and it would be nice to know if it didn't.
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.
As a further suggestion, we can also remove the
set enable_llvm_abi_extensionssince we no longer havei128's in this new minimized test case.