summaryrefslogtreecommitdiff
path: root/src/tools
Commit message (Collapse)AuthorAgeFilesLines
...
* Enable bulk memory by default (#1728)Sam Clegg2021-10-131-1/+3
| | | | | | | | | | | This features was finished earlier this year: https://github.com/WebAssembly/proposals/blob/master/finished-proposals.md One thing to note is that the version of the spec tests we currently have in third_party/testsuite doesn't have bulk memory merged yet so this change disables bulk memory when running some of those tests. This will be removed in a followup when we update the testsuite. Fixes: #1717
* Set features of the Store used in wasm-interp (#1723)Sam Clegg2021-10-121-0/+1
| | | | | | | | | | | Without this change wasm-interp always runs with default features. These features seem to be used in just a single location: src/interp/interp.cc: int pass = store.features().bulk_memory_enabled() ? Init : Check; I noticed this when trying to enable bulk memory but run the interpreter with `--disable-bulk-memory` and it was not effecting this line of code.
* Add objdump flag to print section offsets instead of file offsets (#1696)Derek Schuff2021-08-051-0/+4
| | | Currently implemented just for disassembly. It could be added for other sections/functionality in the future.
* Update exception handling support to current proposal (#1596)Asumu Takikawa2021-02-101-2/+0
| | | | | | | | | | This PR updates the support of exception handling to the latest proposal (that is compatible with future 2-phase exception handling) described in https://github.com/WebAssembly/exception-handling/pull/137 and https://github.com/WebAssembly/exception-handling/pull/143. * Adds back tagged `catch $e`, `catch_all`, and `rethrow N` from a previous version of wabt, but with updates to match the current spec (e.g., `catch_all` shares an opcode with `else`, `rethrow`'s depth indexes only catch blocks, etc). * Adds `unwind` and `delegate` instructions. * Removes `exnref` and `br_on_exn`. * Updates relevant tests. There are some details that could still change (e.g., maybe how `delegate`'s depth is validated), but I'd be happy to submit further PRs if the spec details change.
* Use stderr for all logging and error output (#1579)Sam Clegg2020-12-039-9/+9
| | | | I'm not sure why we were using stdout but the convention is normally to write all logging and error message to stderr.
* Made the interpreter "type-safe" in debug mode (#1512)Wouter van Oortmerssen2020-08-101-1/+3
| | | | | Adds a type field to `Value` to verify the right union member is being read. A Wasm module that has been validated shouldn't need this, but any code reading the wrong value would trigger UB, but still often work (like a uint32_t read from a uint64_t on little endian machine), and mask bugs. Turning this on found bugs in the PR I just landed (as I suspected) but also in older code.
* wast2json: improved file error handling (#1511)Oliver Horn2020-08-101-4/+11
| | | | The result values of the `WriteToFile` calls for `json_stream` and `module_streams` are now evaluated and checked.
* Add tools to use LLVM's libFuzzer (#1507)Ben Smith2020-08-031-0/+30
| | | | This is useful for reproducing bugs found by oss-fuzz (see https://bugs.chromium.org/p/oss-fuzz/issues/list?q=wabt)
* [decompiler] fixed blocks with params. (#1497)Wouter van Oortmerssen2020-07-231-7/+9
| | | | It would previously assume the blocktype is "simple" (at most a single result value), but now also supports function signatures. Also fixed it ignoring the validator result.
* Reference types changes to remove subtyping (#1407)Ben Smith2020-05-281-33/+25
| | | | | | | | Main changes: * Rename `anyref` -> `externref` * Remove `nullref` * Rename `hostref` -> `externref` * `ref.null` and `ref.is_null` now have "ref kind" parameter * Add ref kind keywords: `func`, `extern`, `exn`
* wasi: Implement more of the wasi API (#1430)Sam Clegg2020-05-211-3/+28
| | | | | | | | | | | | | | | | I've been used the tests from wasi-sdk to get started: https://github.com/WebAssembly/wasi-sdk/tree/master/tests All these tests now pass. Still this isn't saying much, there are still some big missing pieces. Started using the new serdes (serialize/deserialze) API in uvwasi. I think we are almost at the point were we can look at auto-generating some of this stuff from witx to avoid having the hand code all this marshelling stuff. Add support for ArgumentCount::ZeroOrMore to OptionParser and also the ability to force the end of option processing using `--`. This allows is to pass options through the underlying wasi program when running wasm-interp.
* Implement more WASI APIs (#1423)Sam Clegg2020-05-161-3/+19
| | | | This is almost enough to pass all the tiny tests in the wasi-sdk repo.
* Use stderr for reporting errors in wasm-interp (#1422)Sam Clegg2020-05-131-5/+7
| | | | We should probably send traving to stderr too but thats a bigger change.
* Add initial MVP of WASI API support to wasm-interp (#1411)Sam Clegg2020-05-121-28/+97
| | | | | | | | | | This is proof of concept that only implements the `proc_exit` and `fd_write` APIs. Extending this to the full WASI API will to follow assuming this approach seems reasonable. Fixes #1409
* Fix typo. NFC. (#1410)Sam Clegg2020-05-111-2/+1
|
* Pass current Thread to host function callbacks (#1412)Sam Clegg2020-05-112-3/+4
| | | | | | | | | | | | | | | The for experimental WASI implementation I'm working on the WASI callbacks (implemented as HostFuncs) need to know which module a call is coming from. This is because the implicitly operate on the memory of the calling instance. This approach seems the match the current convention of passing in the Thread in `Func::DoCall`. The purpose here is to allow the HostCall callback to determine from which instance it is being called. An alternative approach that I considered was created different set of WASI HostCall object for each instance so that instance and its memory we bound to the WASI functions.
* Update testsuite (for SIMD) (#1373)Ben Smith2020-03-251-185/+520
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lots of changes necessary to make this work, as well as some bug fixes. The main change is allowing `nan:canonical` and `nan:arithmetic` as a possible value for each lane of a `v128`. This needs to propogate through the parser, IR, the JSON format, and the spec interpreter. This also changes the format of the spec JSON file, where a SIMD value is now stored as a list of values instead of a single u128: ``` {"type": "v128", "lane_type": "i32", "value": ["0", "0", "0", "0"]} ``` Since the lane type can be `i8` and `i16`, these types can now be used in more places (not just the decompiler). They'll be used for the GC proposal too (for packed values), so I've updated them to use the binary value specified for that proposal. Here are the actual SIMD fixes: * SIMD lanes are malformed if they don't match the binary format, but invalid if they are smaller than the lane width. For example, `i8x16.extract_lane_s` is malformed if the lane is >= 256, because the lane is stored as a byte. But it is invalid if the lane is >= 16. * The `i8x16.narrow_i16x8_u`, `i16x8.narrow_i32x4_u` and `i64x2.load_32x2_u` instructions were not handling sign-extension propoerly. TODO: This code is pretty clumsy now; it would be better to have a universal `Value` and `ExpectedValue` that can be used everywhere, so the logic doesn't need to be duplicated.
* New interpreter (#1330)Ben Smith2020-02-212-346/+404
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's modeled closely on the wasm-c-api. All runtime objects are garbage-collected. The GC'd objects are subclasses of `Object` and all stored in the `Store`. GC roots can be created using a RefPtr<T> struct. The `Module` stores no runtime objects, only description structs (named `*Desc`, e.g. `FuncDesc`). Instantiation takes these descriptors and turns them into runtime objects (e.g. `FuncDesc` is used to create a `Func`). Only import-matching occurs during instantiation; all other validation is assumed to have occurred during Module compilation. As with the previous interpreter, the wasm instructions are not executed directly, and instead compiled to an instruction stream that is easier to interpret (e.g. all branches become gotos). It's still a stack machine, though. The previous interpreter would always compile and instantiate in one step, which means that it was always known whether an imported function is a host function or wasm function. As a result, calls between modules that stayed in wasm could be very cheap (just update PC). Now that the module is compiled before instantiation, an imported function call always has to check first, which may be a slight performance hit. One major difference to the structure of the interpreter is that floating-point values are passed directly, instead of using their equivalent bit pattern. This is more convenient in general, but requires annotating all functions with WABT_VECTORCALL so Visual Studio x86 works properly (otherwise floats are passed in the x87 FP stack). Instruction stream decoding/tracing/disassembling is now all handled in the `Istream` class. This reduces a lot of duplication between the three, which makes the logging-all-opcodes and tracing-all-opcodes less valuable, so I've removed them. Here are the changes to files: binary-reader-metadata.{h,cc} -> [removed] interp-{disassemble.trace}.cc -> istream.{h,cc} There are new helper files: interp-util.{h,cc}: Primarily print debugging functions interp-math.h: Templates used for handling wasm math
* Move ValidateFuncSignatures after ParseModuleWat (#1338)Ben Smith2020-02-211-8/+2
| | | | | | | | | | | | | | Validating function signatures (i.e. making sure a named function type matches its explicit signature) really should be parse of text parsing. Example: (type $F (func (param i32) (result i32))) ... (call_indirect (type $F) (param f32) (result i32) ;; ERROR! This change doesn't quite get us there, but it's closer. The next step will be to remove `ValidateFuncSignatures` entirely and perform those checks in the parser itself.
* Always run ResolveNames after parsing .wast/.wat (#1337)Ben Smith2020-02-203-44/+32
| | | | | | | | | Resolving names (i.e. remapping variable names to indexes) is meant to be part of the parsing process. The spec even considers an unmapped variable name to be "malformed" text. This PR moves in that direction, by always running ResolveNames after parsing text. The next step would be to integrate this more closely with the parser itself.
* wasm-decompile: use symbols from linking section for names. (#1318)Wouter van Oortmerssen2020-01-272-3/+2
| | | | | | | | | | | | This allows wasm .o files to have more readable names, or even final linked modules if the linking information is preserved (with e.g. --emit-relocs in LLD). This is implemented as part of the WABT IR representation, so benefits wasm2wat as well. Named obtained this way are only set for functions if the function doesn't also have a name in the name section, but is preferred over the export name if there is one.
* Update testsuite (#1308)Ben Smith2020-01-161-48/+7
| | | | | | | | | | * Remove `assert_return_func`. This is now handled by using `assert_return` with `(ref.func)`. * The reference types proposal depends on the bulk memory proposal, so using `--enable-reference-types` automatically includes `--enable-bulk-memory`. * `table.fill` no longer clamps to the valid range, and instead checks before writing anything. This matches the other bulk instructions.
* Update testsuite (#1275)Sam Clegg2020-01-091-96/+91
| | | | | | | | | | | | | | | | | The two primary changes involved are: 1. Removal of `assert_return_canonical_nan`/`arithetic nan` in favor of special `nan:canonical`/`nan:arithmetic` constants that can only be used in test expectations. See: https://github.com/WebAssembly/spec/pull/1104 2. New trapping behaviour for bulk memory operations. Range checks are now performed up front for opterations such as memory.fill and memory.copy. See: https://github.com/webassembly/bulk-memory-operations/issues/111 And: https://github.com/webassembly/bulk-memory-operations/pull/123 The old behaviour is still kept around to support table.fill which is defined in reference-types proposal and has yet to be updated.
* Report invalid literals when parsing spectest JSON files (#1288)Sam Clegg2020-01-091-21/+35
| | | | These were being silently ignored previously.
* Add default output name for wast2json (#1287)Sam Clegg2020-01-081-8/+17
| | | Without this the default was to write the wasm files but not the json
* Several fixes for reference types (#1278)Heejin Ahn2020-01-081-0/+6
| | | | | | | - Allow `ref.func` for global initialization expressions - Allow `nullref` as a full-fledged type, after WebAssembly/reference-types#66 - Enable reference types when exnref is used (The reference types proposal is a prerequisite of the EH proposal)
* wasm-decompile: overhauled name filtering. (#1272)Wouter van Oortmerssen2019-12-231-3/+4
| | | | | | | The previous implementation was too simplistic, as it didn't do the renaming at the correct location (such that it can catch all occurrences), and was also very ineffective in cutting down gigantic STL signatures to something managable. This version creates more usable identifiers in almost all cases.
* wabt-decompile: cleaned up string composition. (#1265)Wouter van Oortmerssen2019-12-131-1/+2
| | | | | | | | | | | | | | | | The code had 3 ways of doing string composition: - Using + and += on string/string_view - ostringstream - wabt::Stream Of these, the first was by far the most widely used, simply because decompilation is a hierarchical process, which requires storing intermediate strings before knowing what surrounds them (thus unsuitable for streams). To make the code more uniform, everything was converted to use the first approach. To not get further performance degradations, some more efficient concatenation methods were added, that also work with wabt::string_view.
* Update spec testsuite (#1237)Sam Clegg2019-11-222-15/+34
| | | | | | | The only major change to the interpreter is to move segment initialization out `ReadBinaryInterp` (in the binary reader) and into interp.cc. This is because the test suite now expects out of bound semgments to be reported during initialization rather than reported as validation errors.
* interpreter: Allow traps to include custom error strings (#1236)Sam Clegg2019-11-192-23/+22
| | | | | | | | | | | This means we can give more precise/useful errors for runtime failures. Change interp::Result from an enum to struct so it can hold the result enum plus an optional detailed error message. Add TRAP_MSG and TRAP_IF_MSG macros that work just like TRAP and TRAP_IF but contain a format string and printf-like arguments which are formatted to produce the error message.
* spectest-interp: Report when assert_trap passes and include error string. ↵Sam Clegg2019-11-191-0/+2
| | | | NFC (#1235)
* wasm-interp: Correctly report failure of start function (#1230)Sam Clegg2019-11-181-0/+1
| | | We were printing the error message but returning success.
* wast2json: add new `assert_return_func` assertion type (#1224)Sam Clegg2019-11-151-1/+80
| | | | | This is needed for running the reference-types tests. See: #1223
* Rename v128_bits to simply vec128 since this is stored natively (#1207)Sam Clegg2019-11-111-2/+2
| | | | | | | The _bits suffix is used the floating point types where we use types that differ from the native C types. For v128 we have a native struct type that we store and manipulate directly. Also remove the unneeded bitcast operations.
* wasm-decompile: Fixed arbitrary characters appearing in function names. (#1213)Wouter van Oortmerssen2019-11-111-1/+2
| | | | | In particular, LLD may stick entire C++ signatures in names, that WABT then uses with wasm2wat, but are not appropriate for wasm-decompile function names.
* Add `--version` to wabt tools (#1175)Amir Bawab2019-10-0912-12/+0
| | | | | | | | | | | | | Closes: #1106 Ported versioning system from [Binaryen CMakeLists.txt](https://github.com/WebAssembly/binaryen/blob/dc31b460fef47dfb3415b4ae6276fff4919a03e2/CMakeLists.txt#L10-L23) ``` bin/wasm2c --version 1.0.11-44-g71f883ad ``` Applied to (all) tools in `src/tools/`.
* wasm-decompile: Improved naming. (#1163)Wouter van Oortmerssen2019-09-231-1/+3
| | | | | | This was initially using the same names generated for the wat format. Modified the GenerateNames function slightly to allow alpha based names with no $ prefix, which appears to make for less "noisy" looking code.
* [WIP] Added initial skeleton code for wasm-decompile. (#1155)Wouter van Oortmerssen2019-09-121-0/+114
| | | | | | * [WIP] Added initial skeleton code for wasm-decompile. * Code review changes.
* Fix some bugs w/ wast2json and SIMD (#1140)Ben Smith2019-08-101-1/+2
| | | | | * Never allow a null options pointer to `ParseWatModule` or `ParseWastScript` * Allow a token of type Int or Nat when parsing a simd float const
* Add support for Features to wasm-opcodecnt and emit total instruction count. ↵nlewycky2019-08-101-0/+13
| | | | (#1138)
* Add spec test support for V128. (#1110)nlewycky2019-07-171-0/+12
| | | | | | | | | | | | | | | | | | | | | | * Add spec test support for V128. * This algorithm, however simple, produces the digits in reverse order. Remember to reverse them again before printing. * Correct order of the quads of the v128. Given (v128.const i32x4 0x01020304 0x05060708 0x090a0b0c 0x0d0e0f00), the wabt v128 struct will contain 0x01020304 in v128_bits.v[0]. If a wasm program uses v128.store to store this constant then loads each byte with i32.load8_u, the wabt interpreter produces the order 04 03 02 01, 08 07 06 05, 0c 0b 0a 09, 00 0f 0e 0d. * Add a parser for v128 and implement support in spectest-interp. * Move WriteUint128 to literal.cc, add tests. Rewrite so as to not use string streams. Roll repeated code into a loop. Rename functions to comply with style guide, use anonymous namespace. * Now that v128 has operator==, we can use it here. * In a spectest with a binary module, use the same features for that module as for the outer spectest.
* [interp] Add flag to provide dummy import funcs (#1101)Ben Smith2019-06-281-4/+22
| | | | You can now pass `--dummy-import-func` to `wasm-interp`, which will provide a function that logs the call and returns zero.
* Write assert_exhaustion text to JSON file (#1100)Ben Smith2019-06-281-0/+2
| | | | | | | | | | | The wast file definition for assert_exhaustion looks like: ```wasm (assert_exhaustion (invoke "function" (i32.const 132)) "error message") ``` This commit adds the "error message" part to the output.
* Match custom section names in wasm-objdump (#1097)Ben Smith2019-06-271-1/+3
| | | | | | | | | This way you can see the contents of just one custom section by using: ``` wasm-objdump -j section_name -x ``` Where `section_name` is the name of the custom section.
* Implement bulk memory in the interpreter (#1074)Ben Smith2019-05-071-2/+0
| | | | | | | | | * Implement bulk memory in interpreter * Read/Write elem_type in element segments * Binary format * Text format (`(elem passive funcref...)`) * Add DataSegment runtime objects * Only initialize active data segments when instantiating
* Update testsuite; fix linking spec test (#1055)Ben Smith2019-04-031-2/+3
| | | | | | | | | | When a module is instantiated, and the start function traps, the contents of the memory and the table may have been modified. This case is handled by the `assert_uninstantiable` check in a wast test. In spectest-interp, assert_uninstantiable would instantiate the module, but was incorrectly resetting the environment. In run-spec-wasm2c, the `assert_uninstantiable` tests weren't being run at all. Now the module's `init` function is run, and it is expected to trap.
* Remove LexerSourceFile (#1054)Ben Smith2019-04-014-21/+32
| | | | | | The only benefit to LexerSourceFile is to read files that are larger than can be loaded into memory. That probably is only a valuable feature when loading GB-sized files on a 32-bit machine. I'm not certain that it's worth the extra complexity.
* Rename anyfunc -> funcref; parse reference types (#1026)Ben Smith2019-02-251-1/+1
| | | | | | | | | Also: * Add feature limits on using v128 and anyref types (requires --enable-simd and --enable-reference-types respectively). * Separate out ParseValueType (used for params, locals, global types) from ParseRefType (used for table types).
* Add support for the reference types proposal (#938)Alex Crichton2019-02-141-1/+1
| | | | | | | | | | | | | | | | | | | | * Add support for the reference types proposal This commit adds support for the reference types proposal to wabt. Namely it adds new opcodes like `table.{get,set,grow}` as well as adds a new `anyref` type. These are plumbed throughout for various operations in relatively simple fashions, no support was added for a subtyping relationship between `anyref` and `anyfunc` just yet. This also raises the restriction that multiple tables are disallowed, allowing multiple tables to exist when `--enable-reference-types` is passed. * Allow nonzero table indices in `call_indirect` Plumb support throughout for the `call_indirect` instruction (and `return_call_indirect`) to work with multi-table modules according to the reference types proposal.
* Return failed tests count from spectest-interp (#1003)Ben Smith2019-02-011-9/+13
| | | | | | | `spectest-interp` used to return 0 (success) when tests failed, and non-zero only if the source could not be parsed. It's more useful to return non-zero if the tests fail too. Fixes issue #1002.
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-05 08:17:26 +0000