| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This continues the work from #1783 and reduces special handling of elem
exprs, by treating them the same as other const expressions (init
expressions).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
I'm not sure why we were using stdout but the convention is normally to
write all logging and error message to stderr.
|
|
|
| |
Signed-off-by: Radu M <root@radu.sh>
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
This is in preparation for updating to latest version reference-types
proposal where there is an additional flag and they can be combined.
See: https://github.com/WebAssembly/bulk-memory-operations/issues/98
Also, add ERROR_IF to binary-reader.cc as logical corollary to the
existing ERROR_UNLESS.
|
|
|
|
|
| |
* Store element segments as a vector of `ElemExpr`, instead of func index
* Read/write binary format for each element expression
* Read/write text format for each element expression
|
|
|
|
|
|
|
|
|
| |
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).
|
|
|
| |
This is useful for finding large functions with wasm-objdump.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit starts to add support in wabt's various tools for the
upcoming [bulk memory proposal][1]. This is based off the current
proposal's overview, although these may get tweaked over time!
This is also the first time I've significantly contributed to wabt, and
what I thought would be a relatively simple addition ended up being much
larger than I imagined! I didn't add many negative tests yet but if more
tests are desired please let me know!
[1]: https://github.com/webassembly/bulk-memory-operations
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Remove `run-objdump.py`; replace with `RUN` cmds
This CL introduces two new TOOLs for tests:
* `run-objdump-gen-wasm`: Run objdump on wasm files generated by
`gen-wasm.py`.
* `run-objdump-spec`: Run objdump on wasm files generated by
`wast2json`. For now, this requires each test to specify the files
manually: `%(temp_file)s.0.wasm %(temp_file)s.1.wasm` etc.
`gen_wasm_py` has been added as a new RUN variable as well.
* Call FixPythonExecutable after expanding variables
|
|
|
|
| |
As suggested in https://github.com/WebAssembly/wabt/pull/725#discussion_r162516714.
|
| |
|
|
|
|
| |
This is more consistent with how llvm and binutils
name such tools.
|
|
|
|
|
| |
The expected test output was out of sync becasue whitespace
at the start and end of stdout doesn't cause test failures
(because stdout/stderr are stripped before comparison).
|
| |
|
|
|
|
|
| |
Without this objdump doesn't show the final byte/opcode
of each function.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Update wasm binary format label to 1
Rebaseline tests, but no other changes.
* Revert test/spec/globals.txt
* Update testsuite
* Update spec binary.wast test and testsuite repo
|
| |
|
|
|
|
|
|
|
| |
* Make some binary reading/writing utilities public
This is mostly a refactor to make some of the internal
binary reading/writing utilities public and available
to the wasm linker prototype that I'm working on.
|
| |
|
| |
|
|
|
|
|
| |
* Wasmdump improvments
fixes #167
|
|
|
|
|
|
|
|
| |
* wasmdump improvments
- Split into three different passes: headers, details, and raw
- Nest imports correctly
- Show element count as part of section header rather than on its
own line
|
|
|
|
|
|
|
| |
* All types are unified (i32,i64,f32,f64,func,anyfunc,void)
* Can't use array to get type name; use `wasm_get_type_name` instead
* Encode types as vs7 (i.e. Signed LEB128 with max length 1 byte)
* Change version to 0xd
|
| |
|
|
|
|
| |
converted another batch
|
|
|
|
|
|
| |
* Add wasmdump binary for inspecting wasm files
Run this tool to as part of the 'dump' tests rather
than using the -d flag to wast2wasm.
|
| |
|
| |
|
|
|
|
| |
This fixes #132.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
v8 also has support for the names section, but I'll add that later.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
I broke this when I rewrote everything.
|
|
|
|
|
| |
This was originally done because it was difficult to do otherwise with
the old binary generator.
|