From a5919e92af2e1ef9172d541f1b30d143d5f96e56 Mon Sep 17 00:00:00 2001 From: Ben Smith Date: Wed, 3 Apr 2019 11:36:14 -0700 Subject: 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. --- third_party/testsuite | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'third_party') diff --git a/third_party/testsuite b/third_party/testsuite index 8efdcbea..1e6b3836 160000 --- a/third_party/testsuite +++ b/third_party/testsuite @@ -1 +1 @@ -Subproject commit 8efdcbeaeba16493f1f360532754456a5a83bf3d +Subproject commit 1e6b3836e97ddbb90f4520ff18411dcfabaf0354 -- cgit v1.2.3