Signature mismatch when built with bulk memory + wasm64

[RReverser]

(Split out from #20549.)

It appears that bumping browser versions in that PR makes BULK_MEMORY enabled by default, as after this bump it's now supported by all engines.

That, in turn, breaks wasm64 tests because bulk memory seems incompatible with wasm64 at the moment, or rather emscripten_memset_bulkmem is due to wrong signature:

+RuntimeError: Aborted(CompileError: WebAssembly.instantiate(): Compiling function #15:"emscripten_memset_bulkmem" failed: memory.fill[2] expected type i32, found local.get of type i64 @+1859)
+    at abort (/tmp/emtest_fsexcy95/emscripten_test_other_8gw_9wy3/a.out.js:666:11)
+    at /tmp/emtest_fsexcy95/emscripten_test_other_8gw_9wy3/a.out.js:780:5
+Thrown at:
+    at abort (/tmp/emtest_fsexcy95/emscripten_test_other_8gw_9wy3/a.out.js:666:11)
+    at /tmp/emtest_fsexcy95/emscripten_test_other_8gw_9wy3/a.out.js:780:5

This should be fairly easy to reproduce in isolation.

[RReverser]

Hm or maybe it is a Node.js issue? I can reproduce it with Node.js 16.2 that comes with emsdk and is used by test runner, but not with Node.js 20.0 I have installed globally.

[RReverser]

Trying to auto-disable bulk memory for wasm64 if targeting old Node: a3e86b9

[kleisauke]

It looks like support for this landed in V8 10.0.71 with commit v8/v8@18469ec, so Node.js 18 (LTS) would be the minimum supported runtime version for this setting combo.
https://nodejs.org/en/blog/announcements/v18-release-announce#v8-101

[RReverser]

Nice find!