Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: ed1234f879994c4f740c3abd41b09c671e21e847
https://github.com/WebKit/WebKit/commit/ed1234f879994c4f740c3abd41b09c671e21e847
Author: Keith Miller <keith_mil...@apple.com>
Date: 2025-04-28 (Mon, 28 Apr 2025)
Changed paths:
A JSTests/wasm/exception-spec-wast.js
A JSTests/wasm/exception-wast-wrapper.js
A JSTests/wasm/stress/js-tag-rethrow-cross-instance.js
M JSTests/wasm/stress/js-tag-rethrow.js
M Source/JavaScriptCore/runtime/OptionsList.h
M Source/JavaScriptCore/wasm/WasmEntryPlan.cpp
M Source/JavaScriptCore/wasm/WasmFunctionParser.h
M Source/JavaScriptCore/wasm/WasmModuleInformation.h
Log Message:
-----------
Disallow both legacy and modern wasm exceptions in the same module
https://bugs.webkit.org/show_bug.cgi?id=292188
rdar://149032105
Reviewed by Daniel Liu and Yusuke Suzuki.
This PR disables using legacy (deprecated) exceptions in the same wasm module
as modern exceptions (via try_table).
Legacy exceptions are deprecated so we'd like to encourage their disuse. This
PR also matches Chrome/V8's behavior:
Flag introduced: https://chromium-review.googlesource.com/c/v8/v8/+/6433920
Flag enabled by default:
https://chromium-review.googlesource.com/c/v8/v8/+/6439498
There was one test that expected to be able to use both exceptions in the same
module so I rewrote that test
to instead use both across instances.
Canonical link: https://commits.webkit.org/294209@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes
