| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
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.
|
| |
|
|
|
| |
WastParser now handles the abbreviated (no tableidx) forms of
table.{get,set,size,grow,fill} (needed after
https://github.com/WebAssembly/spec/pull/1582).
|
| |
|
|
| |
(#1895)
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
I think it was always intended to work this way but was
left as a TODO.
|
|
|
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.
|
