Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 40d37f36527f72f11f033b0353643099a40437f7
https://github.com/WebKit/WebKit/commit/40d37f36527f72f11f033b0353643099a40437f7
Author: Yusuke Suzuki <[email protected]>
Date: 2026-08-09 (Sun, 09 Aug 2026)
Changed paths:
M JSTests/wasm/js-api/memory64-js-api-errors.js
M JSTests/wasm/js-api/memory64-js-api.js
M JSTests/wasm/stress/memory64-maximum-limits.js
M JSTests/wasm/stress/memory64-oversized-limits.js
M JSTests/wasm/v8/memory64.js
M
LayoutTests/imported/w3c/web-platform-tests/wasm/core/memory64/memory64.wast.js-expected.txt
M Source/JavaScriptCore/runtime/PageCount.h
M Source/JavaScriptCore/wasm/WasmLimits.h
Log Message:
-----------
[JSC] memory64 should accept large sized page numbers in module parsing, and
should reject creation at runtime
https://bugs.webkit.org/show_bug.cgi?id=321372
rdar://184424841
Reviewed by Sosuke Suzuki.
We should do the same to table64. Module parsing should accept very large
number of memory size limits. But we should reject creation / growth at
runtime.
* JSTests/wasm/js-api/memory64-js-api-errors.js:
(assert.throws):
* JSTests/wasm/js-api/memory64-js-api.js:
(assert.throws):
* JSTests/wasm/stress/memory64-maximum-limits.js:
(Math.min):
* JSTests/wasm/stress/memory64-oversized-limits.js:
* JSTests/wasm/v8/memory64.js:
*
LayoutTests/imported/w3c/web-platform-tests/wasm/core/memory64/memory64.wast.js-expected.txt:
* Source/JavaScriptCore/runtime/PageCount.h:
(JSC::PageCount::bytes const):
* Source/JavaScriptCore/wasm/WasmLimits.h:
(JSC::Wasm::maxBufferByteLength):
(JSC::Wasm::static_assert):
Canonical link: https://commits.webkit.org/318874@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
