Sven Sauleau ff6544c5b0 [wasm] fix js-api Memory and Table constructor ... Fix and re-enable tests for WebAssembly's memory/constructor and table/constructor js-api. It introduces the '[EnforceRange] unsigned long' algorithm used to validate initial and maximum properties. The initial property is now required, by the switch to the Web IDL specification. Most of the input validations errors are now considered TypeError instead of RangeError. The WasmTableObject and WasmMemoryObject APIs use more consistently uint32_t to ensure integer range and remove the need for bounds checks. Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Bug: v8:8319 Change-Id: Iedd3ee6484ef688a5e96f93006eb6ca66d805a48 Reviewed-on: https://chromium-review.googlesource.com/c/1354043 Commit-Queue: Adam Klein <adamk@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#58138}		2018-12-10 23:32:05 +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
testcfg.py	Reland "[wasm] Add a new wasm-js testsuite to run js-api tests"	2018-10-18 20:18:55 +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
wasm-js.status	[wasm] fix js-api Memory and Table constructor	2018-12-10 23:32:05 +00:00