[wasm] Update spec tests

R=ecmziegler@chromium.org

Change-Id: Ifead2feecc5786630ab442d125826688dc170e1b
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2534477Reviewed-by: Emanuel Ziegler <ecmziegler@chromium.org>
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#71148}

test/wasm-js/tests.tar.gz.sha1

-331d0b45c9b1fe5872b5b27a7eff2c889cecb495
\ No newline at end of file
+edb6ca6624330832e2e518e2d49dbfefc870addf
\ No newline at end of file

test/wasm-spec-tests/tests.tar.gz.sha1

-a58223f93f7c7489abd950f322f970caac3c2cad
\ No newline at end of file
+20b5cfcabc0bafec783450e9fbf69ebd1fdb4c46
\ No newline at end of file

test/wasm-spec-tests/wasm-spec-tests.status

@@ -10,6 +10,10 @@
   'proposals/bulk-memory-operations/binary': [FAIL],
   # TODO(v8:10994): Failing spec test after update.
   'proposals/reference-types/br_table': [FAIL],
+  'proposals/simd/binary': [FAIL],
+  'proposals/simd/data': [FAIL],
+  'proposals/js-types/data': [FAIL],
+  'proposals/reference-types/binary': [FAIL],
 
   # TODO(v8:9144): The MVP behavior when bounds-checking segments changed in
   # the bulk-memory proposal. Since we've enabled bulk-memory by default, we