-
Notifications
You must be signed in to change notification settings - Fork 747
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
Fuzzer: Remove --emit-js-shell logic and reuse fuzz_shell.js instead #6310
Merged
Merged
Changes from all commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
fec0cfe
work
kripken d8e8644
simpl
kripken 9146a1e
remoof
kripken d5376dc
work
kripken dac18db
fix
kripken 2bd1b53
less
kripken 0109bbb
less
kripken 47b1730
less
kripken 302a18a
stringses
kripken 96e5257
Undollar
kripken cdc6af8
fix
kripken 4932553
fix
kripken cfe01f6
fix
kripken ee04a7c
work
kripken fe38519
work
kripken 2d6938d
work
kripken 9ebf9df
work
kripken b796356
work
kripken 2fcfb7d
Merge remote-tracking branch 'myself/nofuzz.asyncify' into fuzz.shell…
kripken 88f14f7
Merge remote-tracking branch 'origin/main' into fuzz.shell.ALWAYS
kripken 1f01b70
comment
kripken 61f9554
comment
kripken e895eb3
remove js wrapper test
kripken 7e4e1f7
update some test expectations
kripken 24ce771
remove unneeded hack
kripken a24fe48
restore load-bearing hack
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
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 was deleted.
Oops, something went wrong.
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.
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.
What does sending a null for a parameter mean? Does this mean the
null
arg in?
I'm not very familiar with JS still, so I looked it up (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/apply), and it looks the first param is
thisArg
. Do we need this arg? What does converting this to a number/reference mean?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.
Ah, yeah, this could be confusing because
null
is used in two ways. Yes, the first null isthisArg
, which we have to pass only because we are using.apply
. Basically we want to dofor a function with two or three parameters, etc. To do that we want to send a vector of arguments, which means we need to use
apply
, which forces us to provide something forthisArg
. The value there doesn't matter.The nulls that we pass in to the params get converted into wasm types. Sending
null
to ani32
param gives a 0, and to a(ref null any)
gives(ref.null any)
and so forth. The specific values don't matter (though it would be nice eventually to send in more values than0
, but the fuzzer added calls inside the wasm with such things). But we do not want to trap because of a conversion, which would happen if we passed0
because that can't be converted to a(ref null any)
for example.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 see, thanks!
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.
Do we care about supporting non-nullable reference parameters?
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.
In calls from JS I'd say no - we don't have a good way to construct those atm. As mentioned above the fuzzer generates internal calls to exports which gives internal coverage for such functions at least (but not for the JS-wasm boundary, which maybe some day will be important here).