Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 09be1474d0e68e869cf7047db875ca5a6eba4a16
https://github.com/WebKit/WebKit/commit/09be1474d0e68e869cf7047db875ca5a6eba4a16
Author: Daniel Liu <[email protected]>
Date: 2025-10-07 (Tue, 07 Oct 2025)
Changed paths:
A JSTests/wasm/stress/exception-thrown-at-end-of-catch.js
M Source/JavaScriptCore/wasm/WasmIPIntGenerator.cpp
Log Message:
-----------
Fix IPInt catch handler bounds generation
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 catch/catch_all/delegate byte, making a [start, end] interval. When we
walk
exception handlers during unwinding, we treat the intervals as [start, end),
which
means that we will not handle cases where a CallSiteIndex lands exactly on a
catch
bytecode.
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/WasmIPIntGenerator.cpp:
(JSC::Wasm::IPIntGenerator::addCatchToUnreachable):
(JSC::Wasm::IPIntGenerator::addCatchAllToUnreachable):
(JSC::Wasm::IPIntGenerator::addDelegateToUnreachable):
(JSC::Wasm::IPIntGenerator::endTryTable):
Canonical link: https://commits.webkit.org/301170@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
