diff options
author | Alon Zakai <azakai@google.com> | 2024-11-21 11:11:48 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-11-21 11:11:48 -0800 |
commit | af5f74aeb3c53081ffaedbde18a77bdede0a697e (patch) | |
tree | 2dd7e09ad82e4d918f9d579c964fb8f25833f906 /src/wasm2js.h | |
parent | 45d8f24ad36562939bed14b2157fd5bb51c396bc (diff) | |
download | binaryen-af5f74aeb3c53081ffaedbde18a77bdede0a697e.tar.gz binaryen-af5f74aeb3c53081ffaedbde18a77bdede0a697e.tar.bz2 binaryen-af5f74aeb3c53081ffaedbde18a77bdede0a697e.zip |
Fuzzing: Append more JS operations in run.py (#7098)
The main fuzz_shell.js code builds and runs the given wasm. After the refactoring
in #7096, it is simple to append to that file and add more build and run operations,
adding more variety to the code, including cross-module interactions. Add logic
to run.py to do that for ClusterFuzz.
To test this, add a node test that builds a module with internal state that can
actually show which module is being executed. The test appends a build+run
operation, whose output prove that we are calling from the first module to the
second and vice versa.
Also add a ClusterFuzz test for run.py that verifies that we add a variety of
build/run operations.
Diffstat (limited to 'src/wasm2js.h')
0 files changed, 0 insertions, 0 deletions