WABT (we pronounce it “wabbit”) is a suite of tools for WebAssembly, including:
These tools are intended for use in (or for development of) toolchains or other systems that want to manipulate WebAssembly files. Unlike the WebAssembly spec interpreter (which is written to be as simple, declarative and “speccy” as possible), they are written in C/C++ and designed for easier integration into other systems. Unlike Binaryen these tools do not aim to provide an optimization platform or a higher-level compiler target; instead they aim for full fidelity and compliance with the spec (e.g. 1:1 round-trips with no changes to instructions).
Wabt has been compiled to JavaScript via emscripten. Some of the functionality is available in the following demos:
Clone as normal, but don't forget to get the submodules as well:
$ git clone --recursive https://github.com/WebAssembly/wabt $ cd wabt
This will fetch the testsuite and gtest repos, which are needed for some tests.
You'll need CMake. If you just run make, it will run CMake for you, and put the result in out/clang/Debug/ by default:
Note: If you are on macOS, you will need to use CMake version 3.2 or higher
$ make
This will build the default version of the tools: a debug build using the Clang compiler.
NOTE: Under the hood, this uses make to run CMake, which then calls make again. On some systems, this doesn't build properly. If you see these errors, you can build using CMake directly as described below.
There are many make targets available for other configurations as well. They are generated from every combination of a compiler, build type and configuration.
gcc, clang, gcc-i686, gcc-fuzzdebug, releaseasan, msan, lsan, ubsan, no-re2c, no-testsThey are combined with dashes, for example:
$ make clang-debug $ make gcc-i686-release $ make clang-debug-lsan $ make gcc-debug-no-re2c
You can also run CMake yourself, the normal way:
$ mkdir build $ cd build $ cmake .. ...
You‘ll need CMake. You’ll also need Visual Studio (2015 or newer) or MinGW.
You can run CMake from the command prompt, or use the CMake GUI tool. See Running CMake for more information.
When running from the commandline, create a new directory for the build artifacts, then run cmake from this directory:
> cd [build dir] > cmake [wabt project root] -DCMAKE_BUILD_TYPE=[config] -DCMAKE_INSTALL_PREFIX=[install directory] -G [generator]
The [config] parameter should be a CMake build type, typically DEBUG or RELEASE.
The [generator] parameter should be the type of project you want to generate, for example "Visual Studio 14 2015". You can see the list of available generators by running cmake --help.
To build the project, you can use Visual Studio, or you can tell CMake to do it:
> cmake --build [wabt project root] --config [config] --target install
This will build and install to the installation directory you provided above.
So, for example, if you want to build the debug configuration on Visual Studio 2015:
> mkdir build > cd build > cmake .. -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_INSTALL_PREFIX=..\bin -G "Visual Studio 14 2015" > cmake --build .. --config DEBUG --target install
If you make changes to src/wast-lexer.cc, you'll need to install re2c. Before you upload your PR, please run make update-re2c to update the prebuilt C sources in src/prebuilt/.
CMake will detect if you don't have re2c installed and use the prebuilt source files instead.
Some examples:
# parse and typecheck test.wat $ out/wat2wasm test.wat # parse test.wat and write to binary file test.wasm $ out/wat2wasm test.wat -o test.wasm # parse spec-test.wast, and write verbose output to stdout (including the # meaning of every byte) $ out/wat2wasm spec-test.wast -v # parse spec-test.wast, and write files to spec-test.json. Modules are written # to spec-test.0.wasm, spec-test.1.wasm, etc. $ out/wast2json spec-test.wast -o spec-test.json
You can use --help to get additional help:
$ out/wat2wasm --help
Or try the online demo.
Some examples:
# parse binary file test.wasm and write text file test.wat $ out/wasm2wat test.wasm -o test.wat # parse test.wasm and write test.wat $ out/wasm2wat test.wasm -o test.wat
You can use --help to get additional help:
$ out/wasm2wat --help
Or try the online demo.
Some examples:
# parse binary file test.wasm, and type-check it $ out/wasm-interp test.wasm # parse test.wasm and run all its exported functions $ out/wasm-interp test.wasm --run-all-exports # parse test.wasm, run the exported functions and trace the output $ out/wasm-interp test.wasm --run-all-exports --trace # parse test.json and run the spec tests $ out/wasm-interp test.json --spec # parse test.wasm and run all its exported functions, setting the value stack # size to 100 elements $ out/wasm-interp test.wasm -V 100 --run-all-exports
You can use --help to get additional help:
$ out/wasm-interp --help
See wasm2c.md
See test/README.md.
To build with the LLVM sanitizers, append the sanitizer name to the target:
$ make clang-debug-asan $ make clang-debug-msan $ make clang-debug-lsan $ make clang-debug-ubsan
There are configurations for the Address Sanitizer (ASAN), Memory Sanitizer (MSAN), Leak Sanitizer (LSAN) and Undefine Behavior Sanitizer (UBSAN). You can read about the behaviors of the sanitizers in the link above, but essentially the Address Sanitizer finds invalid memory accesses (use after free, access out-of-bounds, etc.), Memory Sanitizer finds uses of uninitialized memory, the Leak Sanitizer finds memory leaks, and the Undefined Behavior Sanitizer finds undefined behavior (surprise!).
Typically, you'll just want to run all the tests for a given sanitizer:
$ make test-asan
You can also run the tests for a release build:
$ make test-clang-release-asan ...
The Travis bots run all of these tests (and more). Before you land a change, you should run them too. One easy way is to use the test-everything target:
$ make test-everything
To run everything the Travis bots do, you can use the following scripts:
$ CC=gcc scripts/travis-build.sh $ CC=gcc scripts/travis-test.sh $ CC=clang scripts/travis-build.sh $ CC=clang scripts/travis-test.sh