summaryrefslogtreecommitdiff
path: root/include/wabt
Commit message (Collapse)AuthorAgeFilesLines
* Issue a nicer error message on wasm components. (#2515)Dan Gohman2024-12-061-0/+2
| | | | | | | | | | | | Decode just enough of the component binary format to recognize when the input is a component, and issue a dedicated error message for it. Before: 0000008: error: bad wasm file version: 0x1000d (expected 0x1) After: 0000008: error: wasm components are not yet supported in this tool
* interp: Implement EHv4 (#2512)Soni L.2024-11-201-0/+2
| | | Continuation of #2470
* binary/wat: Implement EHv4 (#2470)Soni L.2024-11-2011-1/+77
| | | | This pull request implements EHv4. Binary is mostly untested until interp is working.
* Add support for the custom-page-sizes proposal (#2502)Keith Winstein2024-11-0812-20/+44
| | | | This adds support in the binary/text parsers and writers, the validator and interpreter, and objdump (but not wasm2c).
* [EH] Fix exnref's opcode (#2492)Heejin Ahn2024-10-211-1/+1
| | | | | `exnref`'s opcode is -0x17: https://github.com/WebAssembly/exception-handling/blob/main/proposals/exception-handling/Exceptions.md#exnref
* type.h: Introduce ExnRef (#2489)Soni L.2024-10-171-1/+5
|
* wasm-interp: Fix catch handlers correctly (#2483)Soni L.2024-10-073-0/+3
| | | local decl count != local count
* wasm2c: Use wrappers for function references (#2465)Soni L.2024-09-231-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Clang 17(?) tightened UBSAN checks, so that you now get this: ``` - test/wasm2c/spec/call_indirect.txt expected error code 0, got 1. STDERR MISMATCH: --- expected +++ actual @@ -0,0 +1,3 @@ +out/test/wasm2c/spec/call_indirect/call_indirect.0.c:2144:12: runtime error: call to function w2c_call__indirect__0__wasm_f0 through pointer to incorrect function type 'unsigned int (*)(void *)' +/home/runner/work/wabt/wabt/out/test/wasm2c/spec/call_indirect/call_indirect.0.c:1925: note: w2c_call__indirect__0__wasm_f0 defined here +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior out/test/wasm2c/spec/call_indirect/call_indirect.0.c:2144:12 STDOUT MISMATCH: --- expected +++ actual @@ -1 +0,0 @@ -134/134 tests passed. ``` This happens because emitted functions use a typed module instance, while function references use a `void*` instance. It is UB in C to call the former with the latter, so clang is correct here. We had to pick one of two ways to fix this: either emit `void*` wrapper functions that do the appropriate downcasting for any module functions that go into a table (potentially including imported functions), or the approach that takes significantly less effort of changing everything to `void*` and downcasting internally. ~~We obviously chose the latter.~~ We eventually started emitting wrapper functions.
* Add missing relocation types (and delete a non-existent one) (#2457)SingleAccretion2024-08-291-2/+6
|
* Avoid creating temporary vector copies when checking signature (#2435)Michael Bradshaw2024-06-241-0/+4
|
* Update opcode.def (#2434)ttt2024-06-221-14/+14
| | | The 2nd ret type ​​​​of these opcodes are different from the wasm spec
* Fix typo in token.def (#2433)Michael Bradshaw2024-06-211-1/+1
|
* Update testsuite and implement table64 (#2418)Sam Clegg2024-05-152-9/+13
| | | | | See https://github.com/WebAssembly/memory64/issues/51 Includes workaround for #2422
* Update testsuite and corresponding update to comment parser (#2416)Sam Clegg2024-05-131-2/+2
| | | | | | | The main change here is because `comments.wast` was updated to include a "quoted" module at the top level. Previously quoted modules had only been used as part of invalid or malformed assertion expressions.
* Add support for new WASM_SEGMENT_FLAG_RETAIN segment flag (#2399)Yuta Saito2024-03-111-0/+1
| | | See https://github.com/llvm/llvm-project/pull/81539
* Fix some whitespace in opcode.def. NFC (#2350)Sam Clegg2023-12-091-4/+4
|
* Add support for new WASM_SYMBOL_ABS symbol flag (#2305)Sam Clegg2023-11-281-1/+2
| | | See https://github.com/llvm/llvm-project/pull/67493
* Update ID for tag name subsection (#2336)Michael Williamson2023-11-271-6/+2
| | | | | | | The tag name subsection currently has the speculative ID of 10. However, the extended-name-section proposal has now been updated to use an ID of 11 for the tag name section. This updates the NameSectionSubsection enum accordingly, as well as adding a field name section with the ID of 10.
* wasm2c: implement the tail-call proposal (#2272)Keith Winstein2023-10-242-0/+15
|
* Rename wasm-opcodecnt to wasm-stats (#2298)Soni L2023-09-191-0/+0
|
* WastParser: replace CircularArray with internal TokenQueue (NFC) (#2300)Keith Winstein2023-09-182-125/+16
|
* Implement custom section reading/writing (#2284)Diego Frias2023-09-156-0/+41
|
* Flip order of memory indexes on memory.copy (#2294)Keith Winstein2023-09-116-10/+10
| | | | Reflects change in the multi-memory proposal: https://github.com/WebAssembly/multi-memory/pull/29
* Share reading/validation code between elem exprs & other const exprs (#2288)Keith Winstein2023-09-066-23/+9
| | | | | | This continues the work from #1783 and reduces special handling of elem exprs, by treating them the same as other const expressions (init expressions).
* C++20 compatibility fixesShravan Narayan2023-07-022-3/+3
|
* wasm-objdump: Fix local numbering in disassembly (#2265)Michael Williamson2023-06-271-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, in BinaryReaderObjdumpDisassemble::BeginFunctionBody, we had: local_index_ = objdump_state_->function_param_counts[index]; where index is the index of the function i.e. we treat the keys of function_param_counts as function indices. However, function_param_counts is populated in OnFuncType with: objdump_state_->function_param_counts[index] = param_count; where index is the index of the type i.e. we treat the keys of function_param_counts as type indices. This discrepancy would cause the locals to be incorrectly numbered in the "Code Disassembly" section. This fixes the discrepancy by adding a new field, function_types, which maps from function indices to type indices, and is populated in BinaryReaderObjdump::OnFunction. This field is used in BinaryReaderObjdumpDisassemble::BeginFunctionBody to get the type index for the given function, which is then used to get the parameter count. Fixes #2264.
* memory64: when enabled, check offset range at validation-time (#2253)Keith Winstein2023-06-121-10/+49
| | | | | | | | | | | | | | | | * memory64: when enabled, offset range check is at validation-time Before memory64, the "offset" in a load/store expression was a u32, and we enforced this in the WastParser and BinaryReader. After memory64, the "offset" becomes a u64 syntactically, and the validator checks that it's <= UINT32_MAX for i32 memories. We hadn't been correctly allowing these very large offsets in the text format (even when memory64 was enabled and the memory was i64). (This change also eliminates the "memories" member in the BinaryReader. The BinaryReader no longer needs to keep track of the memories and their types to check well-formedness.)
* WastParser: allow empty modules/scripts with warning (#2248)Keith Winstein2023-06-071-0/+1
|
* wasm2c: partial support for atomic memory opsShravan Narayan2023-05-171-0/+1
|
* Track use of SIMD and exceptions in IR, and CWriter includes support only if ↵Keith Winstein2023-05-082-2/+8
| | | | used (#2226)
* wasm2c: Enable exceptions and simd according to command line flagsShravan Narayan2023-05-021-0/+3
|
* wasm-objdump: Include function names in "init functions" subsection (#2202)Sam Clegg2023-04-203-3/+3
|
* wasm2c: multiple .c outputs (#2146)Yuhan Deng2023-04-051-1/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * wasm2c: multiple .c outputs This enables wasm2c to have multiple .c outputs, which allows parallel compilation of the wasm2c outputs. This is useful when the input WASM module is big. wasm2c takes the number of .c outputs as an argument to `--num-outputs` (defaulting to 1). If the number is equal to 1, the .c output does not change except for two new macro declarations and the ordering of declarations and definitions. If greater than 1, wasm2c outputs change in the following ways: 1) wasm2c outputs a [module-name]-impl.h that includes any module-wide declarations, including: * content of `WriteSourceTop()` * function type declarations * tag types * tag declarations * function declarations * data segments and elem segments declarations Any static declaration become extern in this header. 2) wasm2c outputs [module-name]_i.c for i = [0, ..., number of .c outputs - 1). Any module-wide material is written to [module-name]_0.c, including: * function types, tags, data segments, elem segments * imports and exports * module initialization, instantiation and free 3) For each function implementation, wasm2c assigns it to one output .c file by sorting the function names and partitioning into roughly equal buckets. Alternately, the caller can supply its own assignment function (helpful if it wants the assignments to be more stable in the face of function insertion or deletion).
* Improve lexing and parsing of invalid annotations (again) (#2166)Keith Winstein2023-03-101-1/+1
| | | | | | | | | | | | | | | This adds a bounds-check to WastLexer::GetText to handle the case when the offset is earlier than token_start (e.g. because GetStringToken found a newline in the string and reset token_start to point at it). Also revises GetIdToken -> GetIdChars to stop skipping the initial char in an annotation delimiter, which is an idchar+ but not an id token. Also fixes the WastParser to handle EOF when reading for the end of an annotation, both for code metadata annotations and other kinds. Previously this produced an infinite loop (but only with --enable-annotations). Fixes #2165
* Always do a full roundtrip in run-roundtrip.py (#1661)Sam Clegg2023-02-281-0/+4
| | | | | | | | | | | | | | | | Even when the result is to be printed rather than compared byte for byte with the first version its still good to process the resulting wat output file so that we know we can parse what we generate. Case in point, this changed caused me to fix two latent bugs: 1. We were not correctly parsing events with inline import/export. 2. We were output element segment names even when bulk memory was not enabled (See #1651) The fix for (2) is a little more involved that we might like since for the first time the wat writer needs to know what features are enabled. Fixes: #1651
* Replace MakeUnique with c++14 std::make_unique (#2152)Keith Winstein2023-02-275-53/+8
|
* Add ARM64 windows compatibility (#2140)Changqing Jing2023-02-091-2/+2
| | | Fixes #2139
* wasm2c: serialize types at wasm2c-time (#2120)Keith Winstein2023-01-251-0/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | This makes wasm2c serialize each function type, rather than registering function types at module-initialization time. The serialized function type is the SHA-256 of the mangled param and result types (with a space between params and results). At runtime in call_indirect, a known (immediate) function type is compared against the function type stored in a funcref structure. For call_indirects to functions local to the module, or for any call_indirect when the toolchain merges string constants across compilation units (generally, GCC and clang), this can be done by comparing the pointers to each function type. Otherwise, the actual 32-byte values are compared. The function type IDs can be looked up at runtime with `Z_[modname]_get_func_type`, which matches the API from `wasm_rt_register_func_type`. A new `callback` example demos this. wasm2c does the SHA-256 either by linking against libcrypto or, if not available or if requested via `cmake -DUSE_INTERNAL_SHA256=ON`, by using a vendored (header-only) PicoSHA2. There is no runtime dependency on SHA-256 in the wasm2c runtime or generated modules. This eliminates the last of the per-module state, so this commit also removes the [modname]_init_module() function and the s_module_initialized bool.
* Use inline keyword over WABT_INLINE. NFC (#2092)Sam Clegg2022-12-022-4/+4
| | | | | | I'm not sure this was ever needed. `__inline` and `inline` are identical under msvc: https://learn.microsoft.com/en-us/cpp/cpp/inline-functions-cpp?view=msvc-170 "The __inline keyword is equivalent to inline"
* Reduce code duplication in MemcpyEndianAware definition. NFC (#2087)Sam Clegg2022-12-012-20/+12
|
* Implement Relaxed SIMD proposal (#1994)Marcus Better2022-11-308-8/+92
| | | | | | | | This adds support for the new opcodes from the Relaxed SIMD proposal (https://github.com/WebAssembly/relaxed-simd) behind the "--enable-relaxed-simd" flag. The exception is the f32x4.relaxed_dot_bf16x8_add_f32x4 instruction which is not yet implemented.
* wasm2c: handle duplicate names across module fields (#2035)Keith Winstein2022-11-301-1/+1
|
* interp: Replace condition for including `type` field in `Value` (#2071)Remko Tronçon2022-11-161-1/+2
| | | | | | | | | Value's `type` field was compiled conditionally on the `NDEBUG` define. This causes problems with programs compiling against libwabt that don't define this macro, as the Value layout no longer matches. Using a condition in config.h. Fixes #2069
* Switch from `typedef` to using `using` in C++ code. NFC (#2066)Sam Clegg2022-11-1511-112/+112
| | | | This is more modern and (IMHO) easier to read than that old C typedef syntax.
* Prefer `constexpr` over `static const`. NFC (#2065)Sam Clegg2022-11-159-19/+19
| | | IIUC this is preferred in modern C++ and expresses indent better.
* Use C++ versions of standard headers. NFC (#2064)Sam Clegg2022-11-154-6/+6
|
* add missing include (#2063)walkingeyerobot2022-11-151-0/+1
| | | Co-authored-by: Mitch Foley <mitchfoley@chromium.org>
* Update testsuite (#2054)Sam Clegg2022-11-131-2/+5
| | | | | | | | | | | | | | | As well as the testsuite update there are two notable changes that come with it here. These can both be split out an landed first if it makes sense. 1. wasm2c now supports element sections containing externref. Currently only the null reference is supported. 2. element segments no longer use funcref as the default element type but instead, unless explicitly included in the binary, the element type defaults to the type of the table in which the segment is active. Fixes: #1612 #2022
* Convert type checks to assertions in the interpreter. NFC (#2055)Sam Clegg2022-11-111-1/+1
| | | | | | | | All of these checks represent cases where a validation error would prevent the type mismatch. When debugging #2054 this check actually worked against me since it was resulting a false-positive "out-of-bound" error reports when really it was an internal type inconsistency (a bug).
* Align `memory.copy` arg types with `memory64` proposal (#2024)Adam Bratschi-Kaye2022-11-011-1/+1
| | | | | | | | | | | | | | | | | | | When both the multi-memory and memory64 features are enabled it's possible for memory.copy to copy between two memories of different types. In this case, the memory64 proposal specifies that the src and dst arguments should correspond to the types of the memory they are accessing, and the size argument should correspond to the "minimum" of the two memory types [1]. That is, the size should be an i32 if either of the memories has type i32 and it should be i64 if both of the memories have type i64. The existing code just expects all three arguments to match the type of the source memory which works whenever the source and destination memories have the same type. This change adjusts that logic to agree with the memory64 proposal in the cases where the two memories have differing types. [1] https://github.com/WebAssembly/memory64/blob/5bfb70d9888b96a2f3d6412ed3599b91364da610/proposals/memory64/Overview.md?plain=1#L211
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-04 18:50:02 +0000