diff options
| author | Ben Smith <binjimin@gmail.com> | 2019-04-03 11:36:14 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-04-03 11:36:14 -0700 |
| commit | a5919e92af2e1ef9172d541f1b30d143d5f96e56 (patch) | |
| tree | 541547fc477dbae8f9aa850298fb33ff38f5fb80 /test/wasm2c/spec | |
| parent | d7d7945a4823a666d5d967f7cb2069cf8797b7d7 (diff) | |
| download | wabt-a5919e92af2e1ef9172d541f1b30d143d5f96e56.tar.gz wabt-a5919e92af2e1ef9172d541f1b30d143d5f96e56.tar.bz2 wabt-a5919e92af2e1ef9172d541f1b30d143d5f96e56.zip | |
Update testsuite; fix linking spec test (#1055)
When a module is instantiated, and the start function traps, the
contents of the memory and the table may have been modified. This case
is handled by the `assert_uninstantiable` check in a wast test.
In spectest-interp, assert_uninstantiable would instantiate the module,
but was incorrectly resetting the environment. In run-spec-wasm2c, the
`assert_uninstantiable` tests weren't being run at all. Now the module's
`init` function is run, and it is expected to trap.
Diffstat (limited to 'test/wasm2c/spec')
| -rw-r--r-- | test/wasm2c/spec/linking.txt | 2 | ||||
| -rw-r--r-- | test/wasm2c/spec/start.txt | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/test/wasm2c/spec/linking.txt b/test/wasm2c/spec/linking.txt index 57c26103..6f9739e2 100644 --- a/test/wasm2c/spec/linking.txt +++ b/test/wasm2c/spec/linking.txt @@ -1,5 +1,5 @@ ;;; TOOL: run-spec-wasm2c ;;; STDIN_FILE: third_party/testsuite/linking.wast (;; STDOUT ;;; -79/79 tests passed. +82/82 tests passed. ;;; STDOUT ;;) diff --git a/test/wasm2c/spec/start.txt b/test/wasm2c/spec/start.txt index d3bb9590..7caafc65 100644 --- a/test/wasm2c/spec/start.txt +++ b/test/wasm2c/spec/start.txt @@ -4,5 +4,5 @@ spectest.print_i32(1) spectest.print_i32(2) spectest.print() -6/6 tests passed. +7/7 tests passed. ;;; STDOUT ;;) |