Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 0b99951396c782f08c1ddaf14bdedfcf4ebbce08
https://github.com/WebKit/WebKit/commit/0b99951396c782f08c1ddaf14bdedfcf4ebbce08
Author: Daniel Liu <[email protected]>
Date: 2025-10-06 (Mon, 06 Oct 2025)
Changed paths:
A JSTests/wasm/stress/exception-thrown-at-end-of-catch.js
M Source/JavaScriptCore/wasm/WasmHandlerInfo.cpp
Log Message:
-----------
Wasm catch handler ranges should be inclusive
https://bugs.webkit.org/show_bug.cgi?id=299629
rdar://161438523
Reviewed by Yusuke Suzuki.
During generation of catch handlers, we set the ending PC to be the exact
position
of the end of the try block, thus creating a [start, end] interval. When we
unwind
and check for exception handlers, however, we treat the intervals as [start,
end),
meaning that we will not handle edge cases where a CallSiteIndex is exactly at
the
end of the interval, thus allowing some exceptions to erroneously propagate.
Test: JSTests/wasm/stress/exception-thrown-at-end-of-catch.js
* JSTests/wasm/stress/exception-thrown-at-end-of-catch.js: Added.
* Source/JavaScriptCore/wasm/WasmHandlerInfo.cpp:
(JSC::Wasm::HandlerInfo::handlerForIndex):
Canonical link: https://commits.webkit.org/301090@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-changes
