| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
This applies the same defaults for features in the JavaScript-compiled
version as the native tools. Without this change, enabling only the
"reference_types" feature did not work, as it got turned off due to
the dependency on "bulk_memory", which is counter-intuitive (see
Features::UpdateDependencies()).
Additionally, exposes all the features and their default setting in
JavaScript.
|
| |
|
|
|
| |
* Log all lexing errors in WastLexer (rather than via parser)
* Update docs/demo/libwabt.js
|
| | |
|
| |
|
| |
Not sure how this line got removed...
|
| |
|
|
|
|
|
| |
libwabt.js is meant to be included in multiple environments (web,
node.js, etc.) so it shouldn't be using NODERAWFS. A recent change to
the build system include `-s NODERAWFS` for all link steps, but those
are only needed for the wabt executables (e.g. wasm2wast.js).
|
| | |
|
| |
|
|
|
|
| |
* Recompile libwabt.js using latest emscripten
* Add features checkbox for wasm2wat (like wat2wasm)
* Remove call to `_wabt_resolve_names_module`, since that's always
done now when parsing text
|
|
|
It's easier to update than gh-pages
|
