Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: d6d09268899bff2ceb25fac7da00a0bc0cbb77eb
https://github.com/WebKit/WebKit/commit/d6d09268899bff2ceb25fac7da00a0bc0cbb77eb
Author: Sergey Rubanov <[email protected]>
Date: 2026-08-04 (Tue, 04 Aug 2026)
Changed paths:
A JSTests/wasm/stress/memory64-bbq-bounds-checking.js
M Source/JavaScriptCore/wasm/WasmBBQJIT.h
M Source/JavaScriptCore/wasm/WasmBBQJIT64.h
M Source/JavaScriptCore/wasm/WasmModuleInformation.h
M Source/JavaScriptCore/wasm/WasmOMGIRGenerator.cpp
Log Message:
-----------
[JSC][Wasm] Force BoundsChecking for Memory64 accesses in BBQ
https://bugs.webkit.org/show_bug.cgi?id=308683
Reviewed by Cole Carley and Keith Miller.
Signaling memory mode relies on 32-bit addresses and a PROT_NONE redzone.
Memory64 cannot use that scheme, so compilers must always emit explicit
bounds checks for Memory64 (and for non-zero multi-memories). Put that
policy on ModuleInformation::memoryModeForAccess and use it from BBQ and
OMG. Keep RELEASE_ASSERT_WITH_SECURITY_IMPLICATION(!isMemory64()) on
Signaling paths so a wrong mode selection still hard-fails.
* Source/JavaScriptCore/wasm/WasmModuleInformation.h:
* Source/JavaScriptCore/wasm/WasmBBQJIT.h:
* Source/JavaScriptCore/wasm/WasmBBQJIT64.h:
* Source/JavaScriptCore/wasm/WasmOMGIRGenerator.cpp:
* JSTests/wasm/stress/memory64-bbq-bounds-checking.js: Added.
Canonical link: https://commits.webkit.org/318602@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
