summaryrefslogtreecommitdiff
path: root/test/spec
Commit message (Collapse)AuthorAgeFilesLines
* Issue a nicer error message on wasm components. (#2515)Dan Gohman2024-12-064-20/+20
| | | | | | | | | | | | 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-202-0/+60
| | | Continuation of #2470
* binary/wat: Implement EHv4 (#2470)Soni L.2024-11-201-1/+1
| | | | 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-083-2/+74
| | | | This adds support in the binary/text parsers and writers, the validator and interpreter, and objdump (but not wasm2c).
* test: Move legacy exception handling tests (NFC) (#2498)Soni L.2024-10-318-113/+113
|
* Update testsuite (#2495)Keith Winstein2024-10-3027-647/+1480
| | | | | The memory64 `table.wast` test has started to depend on function-references and gc (which WABT doesn't support yet), so vendor an older version of the test.
* interp: Handle ref.null exn (#2497)Soni L.2024-10-291-0/+6
|
* Raise parse error on NaN in i32 and i64 literals (#2485)James Ring2024-10-082-0/+16
| | | | Previously, the parser would return result::Error, but would not populate an error message.
* Fix error message for ref.is_null (#2471)Soni L.2024-09-231-1/+2
| | | | Fixes #2453 in a bit of a silly way. (Conveniently, we already have tests for this, but nobody noticed they were broken.)
* Update testsuite and implement table64 (#2418)Sam Clegg2024-05-1515-104/+3899
| | | | | See https://github.com/WebAssembly/memory64/issues/51 Includes workaround for #2422
* Update testsuite and corresponding update to comment parser (#2416)Sam Clegg2024-05-1320-594/+804
| | | | | | | 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.
* Update testsuite (#2287)Keith Winstein2023-10-2412-599/+350
|
* Share reading/validation code between elem exprs & other const exprs (#2288)Keith Winstein2023-09-067-30/+29
| | | | | | This continues the work from #1783 and reduces special handling of elem exprs, by treating them the same as other const expressions (init expressions).
* BinaryReader/Writer: roundtrip large memory64 offsets (#2255)Keith Winstein2023-06-201-6/+6
| | | With memory64, the offset becomes a u64.
* memory64: when enabled, check offset range at validation-time (#2253)Keith Winstein2023-06-126-26/+48
| | | | | | | | | | | | | | | | * 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.)
* spectest-interp: assert_malformed must error in reader alone (#2252)Keith Winstein2023-06-124-8/+4
| | | | | | Previously assert_malformed was treated the same as assert_invalid Also fixes a bug where spectest-interp wasn't trying to validate text modules (e.g. `(assert_invalid (module quote "...") "")`).
* BinaryReader/BinaryReaderIR: check for missing end markers (#2218)Keith Winstein2023-05-033-3/+3
|
* binary-reader.cc: expand max local count and fix error message (#2173)Keith Winstein2023-03-154-8/+8
| | | | | * binary-reader.cc: expand max local count and fix error message Fixes #1593
* Add new tests (#2168)Keith Winstein2023-03-1338-0/+559
| | | | | | | | | | | | | | | | | Fixes a wasm2c bug where instantiation was initializing memories before tables. The spec requires tables to be initialized before memories (newly tested in the multi-memory linking0 test). Remaining missing tests are: - multi-memory/memory_copy1.txt (currently blank) - relaxed-simd/relaxed_dot_product.txt (we don't support the i16x8.relaxed_dot_i8x16_i7x16_s instruction) And for wasm2c only: - five SIMD tests (https://github.com/WebAssembly/wabt/pull/2021#issuecomment-1396386135) - all relaxed-simd and tail-call tests
* Update testsuite (#2167)Keith Winstein2023-03-1315-142/+142
| | | | | WastParser now handles the abbreviated (no tableidx) forms of table.{get,set,size,grow,fill} (needed after https://github.com/WebAssembly/spec/pull/1582).
* Implement Relaxed SIMD proposal (#1994)Marcus Better2022-11-306-0/+36
| | | | | | | | 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.
* Update testsuite (#2054)Sam Clegg2022-11-136-267/+294
| | | | | | | | | | | | | | | 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
* Add tail-call spec tests and fix related parser issue (#2049)Sam Clegg2022-11-082-0/+156
| | | Fixes: #2018
* WastLexer: log lexing errors directly (#2013)Keith Winstein2022-10-031-0/+3
| | | | | * Log all lexing errors in WastLexer (rather than via parser) * Update docs/demo/libwabt.js
* Add tokens test + adjust Wast lexing to match updated spec (#2001)Keith Winstein2022-10-031-0/+113
| | | | | * Update testsuite (adding new tokens.txt test) * Adjust Wast lexing to match updated spec (WebAssembly/spec#1499)
* Update spec tests (#2003)Marcus Better2022-09-2211-615/+673
|
* Track locations of Vars in BinaryReaderIR and BinaryReaderInterp (#1963)Keith Winstein2022-08-1532-147/+147
| | | | - Rebase test output to match new location tracking on Vars - Eliminate single-argument Var() constructor.
* update br_table validation rule + enforce module validity in spectest-interp ↵Keith Winstein2022-04-13171-184/+171
| | | | (#1895)
* Fix checking of ref.func index declarations (#1894)Asumu Takikawa2022-04-131-14/+0
| | | | | | | | | | | The validation was overly strict for ref.func index uses. In the spec, the ref index just needs to appear in "the set of function indices occurring in the module, except in its functions or start function." which includes uses in the global and export sections. Fixes issue #1893
* Update testsuite. (#1872)Zoltan Herczeg2022-03-304-13/+14
|
* Fix function body start/end locations in wasm-validate (#1842)Sam Clegg2022-03-0228-181/+181
| | | | | | | | | | For text validation, this means the error is always correctly reported on the final expression in the function. For binary validation, this means that we report the byte after the last instruction in the function as the failure location. This is in line with other binary validation reports. For example, for `type mismatch in i32.add` we report the validation error at the byte *after* the add instruction.
* Initial implementation of extended-const proposal. (#1824)Sam Clegg2022-02-153-0/+272
| | | | | | | | | | The primary changes here are to the interpreter and how it handles initializer expressions. With this change we model these are normal function that we run during module initialization. I imagine we could optimize this further by creating one long function and encoding the `global.set`/`memory.init`/`table.init` into the function itself, but this change seems like a good first step to make the current tests pass.
* Update testsuite (#1795)Sam Clegg2022-01-103-245/+263
| | | | Remove test/binary/bad-function-missing-end.txt which is now covered upstream: https://github.com/WebAssembly/spec/pull/1405
* Remove check from binary-reader-interp.cc that the validator already ↵Sam Clegg2021-12-1328-201/+201
| | | | | | | | | | catches. NFC (#1784) If you leave stuff on the stack at the end of an initializer expression use the same mechanims to report the error as we do for functions etc. In addition, improve such errors so its more obvious what is going on.
* Share validation code between constant expressions and function bodies. NFC ↵Sam Clegg2021-12-106-68/+64
| | | | | | | | | | | | (#1783) Previously we has special cases for initializer expressions (constant expressions). This change paves the way for adding support for extended constant expressions that support a wider range of instructions. This change removes twice as many lines as it adds which shows that this simplification is probably worthwhile even without the pending extensions.
* Add error locations to BinaryReaderInterp (#1780)Sam Clegg2021-12-09128-2277/+2277
| | | | I think it was always intended to work this way but was left as a TODO.
* Add specification tests for exception handling proposal (#1764)Asumu Takikawa2021-12-068-0/+754
| | | | | | | | This PR imports the spec tests from the Wasm testsuite repo and adds infrastructure to run them correctly. * Adds test expectations for exception handling proposal spec tests. * Adds missing tag signature matching code for import tests. * Adds support for the `assert_exception` command used in new tests. * Fix filename normalization for the spec test runner.
* Perform init expression validation outside of the binary reader. NFC (#1770)Sam Clegg2021-12-029-119/+158
| | | | | | | | | | | | | | | | Rather than spocial casing them in the reader we now use the same instruction callbacks for instruction that appear in init expressions as instructions that appear in normal functions. The result of this change is the validation of init expressions is pushed further up the stack. For example, objdump will now quite happily dump modules that use arbitrary instructions in thier init expressions even though they are not valid. To me, this makes sense since objdump does not do instruction validation elsewhere. The change is pre-cursor to allowing a wider variety of instruction to be present in init expressions. See https://github.com/WebAssembly/extended-const
* Add multi-memory feature support (#1751)Yuhan Deng2021-11-3013-7/+1082
|
* Update testsuite (#1765)Sam Clegg2021-11-1968-3831/+3830
|
* Update third_party/testsuite. NFC (#1752)Sam Clegg2021-11-045-5/+25
|
* Update testsuite (#1738)Sam Clegg2021-10-1868-7290/+3243
| | | | | | | | | | | bulk-memory-operations and reference-types were completely removed from the upstream testsuite becuase there were merged into the upstream spec: https://github.com/WebAssembly/testsuite/pull/44 In order to land this I had to disable several spec tests under wasm2c because it lacks support for mutli-table and reference types. I filed #1737 to track this.
* Enable reference types by default (#1729)Sam Clegg2021-10-1336-31/+6
| | | | | | | | | 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 ref types merged yet so this change disables ref types when running some of those tests. This can be removed in a followup when we update the testsuite.
* Enable bulk memory by default (#1728)Sam Clegg2021-10-1317-14/+5
| | | | | | | | | | | 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
* Avoid writing DataCount section when it is not needed. (#1727)Sam Clegg2021-10-132-10/+4
| | | | | | | | | | | Without this change, when bulk memory is enabled, the DataCount is always written when then removed if it proves that its not needed by any instruction. However, if we know there are no data segments we can avoid writing it altogether. This happens to be more compact but I'm hoping to land this now in anticipation of enabled bulk memory by default. Once we do that we don't want all the `dump` tests to include the writing and truncating of the DataCount section in cases when there is no data.
* SIMD is now phase 5, enable it by default (#1712)Ng Zhi An2021-09-2056-56/+0
| | | | | * SIMD is now phase 5, enable it by default * Update test flags, rebase test, and docs
* [EH] Replace event with tag (#1678)Heejin Ahn2021-06-223-6/+6
| | | | | | | | | | | We recently decided to change 'event' to 'tag', and 'event section' to 'tag section', out of the rationale that the section contains a generalized tag that references a type, which may be used for something other than exceptions, and the name 'event' can be confusing in the web context. See - https://github.com/WebAssembly/exception-handling/issues/159#issuecomment-857910130 - https://github.com/WebAssembly/exception-handling/pull/161
* Memory64: support 64-bit data init-expr (#1656)Wouter van Oortmerssen2021-04-051-1/+1
|
* [simd] Unskip more tests (#1648)Ng Zhi An2021-03-234-5/+37
| | | | Missed unskipping these in prior implementations. With this, all simd tests are now running.
* [simd] Implement store lane (#1647)Ng Zhi An2021-03-224-4/+48
|
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-04 22:23:24 +0000