-
Notifications
You must be signed in to change notification settings - Fork 835
Fuzzer: Add SIMD support to DeNaN #6318
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
Merged
Changes from 1 commit
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
aefdf03
start
kripken 43bb800
sad
kripken 2a75520
work
kripken 7c7ff81
fix
kripken 44e6c86
fix
kripken 96469aa
fix
kripken 0cea4f4
work
kripken d195c00
work
kripken 42e81f2
finish
kripken d970d6a
work
kripken d4bfec9
format
kripken 66c2c50
comment
kripken eaf35dc
Merge remote-tracking branch 'origin/main' into fuzz.simd.nan
kripken c08fa5d
feedback
kripken cf07915
format
kripken 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
fix
- Loading branch information
commit 96469aa00dc71e69c9bf84496df48d338da9e181
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
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.
It would be useful to write the tests using
f32x4andf64x2shapes rather thani32x4so we can better see what values are being passed. You can use the--new-wat-parserand its extensive support for the standard nan formats if you want.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.
I was actually thinking it is nice to see the actual bits because of how they are used in the pass (the explanation about the f32 and f64 bits overlapping etc.)?
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.
To be more specific, in this test code:
It is nice to see the bits, because that allows the comments to clarify how the same bits can be both f32 and f64 nans, or not.
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.
I would be more convinced by this if readers were likely to know off the top of their heads what bit patterns correspond to NaNs. I know I don'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.
Heh, I don't know that either, but I mentioned it in the pass (8 vs 11 top non-sign bits).