| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This finishes #985. This
- replaces the old names in the tests with the new names
- drops support for the deprecated names
- renames test files to match new instruction names
I don't think dropping support for the old names will be a problem at
this point. #985 says the old names are supported for convenience but we
should remove those too at some point; that "some point" may have well
arrived given that three years have passed.
The lists of names updated are in #933, #1564, WebAssembly/spec#720.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
`grow_memory` -> `memory.grow`
`current_memory` -> `memory.size`
This could have been a smaller change, but I took the opportunity to
rename the Token types, Expr types, and callback functions too. Many of
these are sorted alphabetically, so I resorted based on their new names.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add fuzzing helper scripts, fix fuzzing bugs
The fuzzing dictionary was old, so I updated it. Also, I've added some
simple fuzzing shell scripts that make it a bit easier to run.
Bug fixes:
* Validate function index in local name section before calling callback.
* Fix invalid assert in parse_{float,double}_infinity, which assumed
that "infinity" is required (it could be "inf").
* Bail out of resolve local names if there is no current function (e.g.
if attempting to resolve names in an elem offset expression).
* Catch bad_alloc in wast2wasm and wasm2wast. Without this, afl-fuzz
will see allocation failure as a crash.
* disable exceptions by default, add option, wrap tools in try/catch
|
| |
|
|
|
|
|
|
|
|
| |
* ast.{cc,h} => ir.{cc,h}
* binary-reader-ast.{cc,h} => binary-reader-ir.{cc,h}
* ast-writer.{cc,h} => wat-writer.{cc,h}
Everything else changes ast => wast.
When deciding between wast vs. wat, the wat format should only allow for
a single module, without assertions.
|
| |
|
|
|
|
| |
* Change assertions in apply-names to failures
* Fix off-by-one bug in binary-reader-ast get_label_at
* Keep track of last known section code, so the same section cannot be
specified twice, with a custom section between.
|
| | |
|
|
|
Looks like gcc is a little more strict about potentially unused
variables.
|
