| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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>
|
|
|
| |
This is useful for finding large functions with wasm-objdump.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
|
|
|
|
|
|
|
| |
* 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.
|
|
|
|
|
| |
I originally did this to match the old binary generator, but it's not
necessary.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The big changes:
- there are no more statement ops, everything is an expression op
- some of the opcodes are shuffled around
- loops no longer implicitly branch to the top
- loops have two break scopes, one is the continue scope, the deeper one
is the exit scope.
- the return statement was removed, so to return you need to break to a
top-level block
|
|
|
|
|
|
| |
There is now one signature table, and all functions, function types, and
imports reference it by index. This is in preparation for properly
supporting call_indirect.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new binary format has optional sections, which are marked with a
byte. The names and segment data must come after all the sections.
The other major change to the format is that function bodies are now
inlined with the function header. This makes it much easier to append
the assert_* functions to the module after the fact; we can place the
function section last, and write the assertion functions directly into
the buffer.
The only tricky part is that the function count is now stored as leb128,
which means that we may need to shift the function section down when the
function count increases.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the comment characters for the s-expression format so the test files
can easily be loaded into sexpr-wasm directly:
;;; KEY: VALUE
(;; STDOUT ;;;
some
standard
output
;;; STDOUT ;;)
|
|
|
|
|
| |
I thought this was needed, but it doesn't seem to be anymore (or maybe
it never was).
|
| |
|
|
|
|
| |
The v8-native-prototype doesn't work properly without it.
|
| |
|
| |
|
| |
|
| |
|
|
|