Jakob Kummerow a8b7d47733 [wasm] Bring memory limits up to spec ... Make sure the "initial pages" memory limit is enforced correctly and throws a CompileError when exceeded. Bump the "maximum pages" memory limit to 65536. The --wasm-max-mem-pages flag now controls the "initial pages" limit; the "maximum pages" limit is always 65536 as spec'ed. This CL depends on https://github.com/WebAssembly/spec/pull/1121. Bug: v8:7881, v8:8633 Change-Id: I68d07cef56633b8b8ce3b3d047c14e1096daf547 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2035876 Reviewed-by: Andreas Haas <ahaas@chromium.org> Reviewed-by: Georg Neis <neis@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#66400}		2020-02-24 11:00:16 +00:00
..
BUILD.gn	Reland "[wasm] Add a new wasm-js testsuite to run js-api tests"	2018-10-18 20:18:55 +00:00
LICENSE.testharness	Reland "[wasm] Add a new wasm-js testsuite to run js-api tests"	2018-10-18 20:18:55 +00:00
OWNERS	Use relative paths to OWNERS files	2019-08-12 13:52:52 +00:00
testcfg.py	[wasm] Stage multi-value support	2019-10-22 13:49:52 +00:00
testharness-after.js	Reland "[wasm] Add a new wasm-js testsuite to run js-api tests"	2018-10-18 20:18:55 +00:00
testharness.js	[wasm] fix testharness - unreached_func	2018-11-27 22:37:56 +00:00
tests.tar.gz.sha1	[wasm] Update spec tests	2020-02-18 15:16:38 +00:00
wasm-js.status	[wasm] Bring memory limits up to spec	2020-02-24 11:00:16 +00:00