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/spec/linking.txt | |
| 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/spec/linking.txt')
| -rw-r--r-- | test/spec/linking.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/spec/linking.txt b/test/spec/linking.txt index 5a1e87e6..442c59ec 100644 --- a/test/spec/linking.txt +++ b/test/spec/linking.txt @@ -37,5 +37,5 @@ out/test/spec/linking.wast:335: assert_unlinkable passed: out/test/spec/linking.wast:345: assert_unlinkable passed: error: elem segment is out of bounds: [0, 1) >= max value 0 000002d: error: OnElemSegmentFunctionIndexCount callback failed -91/91 tests passed. +94/94 tests passed. ;;; STDOUT ;;) |