[wasm] Passive element segments don't need a table

This CL fixes a spec violation that new spec tests uncovered.

R=thibaudm@chromium.org
CC=ecmziegler@chromium.org

Change-Id: Ie8ae455117f1c719815bad78f14c3b2c5e404e79
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2122023
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Reviewed-by: Thibaud Michaud <thibaudm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#66885}

src/wasm/module-decoder.cc

@@ -1841,9 +1841,6 @@ class ModuleDecoderImpl : public Decoder {
       *status = WasmElemSegment::kStatusDeclarative;
     } else {
       *status = WasmElemSegment::kStatusPassive;
-      if (module_->tables.size() == 0) {
-        error(pc_, "Passive element sections require a table");
-      }
     }
     *functions_as_elements = flag & kFunctionsAsElementsMask;
     bool has_table_index = (flag & kHasTableIndexMask) &&

test/mjsunit/wasm/bulk-memory.js

@@ -222,3 +222,12 @@ function getMemoryFill(mem) {
   // Should not throw.
   builder.instantiate();
 })();
+
+(function TestPassiveElementSegmentNoMemory() {
+  const builder = new WasmModuleBuilder();
+  builder.addFunction('f', kSig_v_v).addBody([]);
+  builder.addPassiveElementSegment([0, 0, 0]);
+
+  // Should not throw.
+  builder.instantiate();
+})();

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

@@ -24,8 +24,6 @@
   'proposals/multi-value/call': [FAIL],
   'proposals/multi-value/if': [FAIL],
   'proposals/multi-value/func': [FAIL],
-
-  'proposals/bulk-memory-operations/bulk': [FAIL],
 }],  # ALWAYS
 
 ['arch == mipsel or arch == mips64el or arch == mips or arch == mips64', {