Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: d8a913bd3feb8328bbe68664e5e33ef60f34d36c
https://github.com/WebKit/WebKit/commit/d8a913bd3feb8328bbe68664e5e33ef60f34d36c
Author: Cole Carley <[email protected]>
Date: 2026-03-04 (Wed, 04 Mar 2026)
Changed paths:
M JSTests/wasm/spec-harness/wasm-module-builder.js
M JSTests/wasm/stress/memory64-bulk-memory.js
M JSTests/wasm/stress/memory64-grow-and-size.js
M JSTests/wasm/stress/memory64-load-and-store.js
M JSTests/wasm/stress/memory64-overflow.js
M JSTests/wasm/stress/memory64-write-to-address-over-4-gigs.js
M Source/JavaScriptCore/wasm/WasmBBQJIT64.cpp
M Source/JavaScriptCore/wasm/WasmBBQJIT64.h
Log Message:
-----------
Fix Memory64 overflow checks in BBQ
rdar://170851725
https://bugs.webkit.org/show_bug.cgi?id=308356
Reviewed by Keith Miller.
Memory64 bounds checking was not correct. I also stopped zero-extending the 64
bit pointer.
* JSTests/wasm/stress/memory64-bulk-memory.js:
* JSTests/wasm/stress/memory64-grow-and-size.js:
(async test):
* JSTests/wasm/stress/memory64-load-and-store.js:
* JSTests/wasm/stress/memory64-overflow.js:
(test):
(async test): Deleted.
* JSTests/wasm/stress/memory64-write-to-address-over-4-gigs.js:
(test):
* Source/JavaScriptCore/wasm/WasmBBQJIT64.h:
(JSC::Wasm::BBQJITImpl::BBQJIT::emitCheckAndPrepareAndMaterializePointerApply):
Canonical link: https://commits.webkit.org/308634@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
