Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 64153f963497bad197d2231657c2a73c2e9488a4
https://github.com/WebKit/WebKit/commit/64153f963497bad197d2231657c2a73c2e9488a4
Author: Yusuke Suzuki <[email protected]>
Date: 2026-08-04 (Tue, 04 Aug 2026)
Changed paths:
A JSTests/wasm/stress/memory64-unreachable-immediates.js
M
LayoutTests/imported/w3c/web-platform-tests/wasm/core/align.wast.js-expected.txt
M Source/JavaScriptCore/wasm/WasmFunctionParser.h
Log Message:
-----------
[JSC] Wasm Memory64 operands are differently decoded in unreachable code
https://bugs.webkit.org/show_bug.cgi?id=321035
rdar://184068455
Reviewed by Cole Carley.
Wasm unreachable code is decoding memory64 operands differently, causing
wasm parse error. Correctly handling memory64 operands in the same way
to the normal path.
* JSTests/wasm/stress/memory64-unreachable-immediates.js: Added.
(async assertRejected):
*
LayoutTests/imported/w3c/web-platform-tests/wasm/core/align.wast.js-expected.txt:
* Source/JavaScriptCore/wasm/WasmFunctionParser.h:
(JSC::Wasm::FunctionParser<Context>::parseMemoryIndexAndFixupAlignment):
(JSC::Wasm::FunctionParser<Context>::parseUnreachableExpression):
Canonical link: https://commits.webkit.org/318605@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
