Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: b7afce9416a9ef663661eb59613768529ea65101
https://github.com/WebKit/WebKit/commit/b7afce9416a9ef663661eb59613768529ea65101
Author: Sergey Rubanov <[email protected]>
Date: 2026-08-18 (Tue, 18 Aug 2026)
Changed paths:
A JSTests/wasm/stress/consistent-compile-error-function-index.js
M Source/JavaScriptCore/wasm/WasmEntryPlan.cpp
M Source/JavaScriptCore/wasm/WasmEntryPlan.h
M Source/JavaScriptCore/wasm/WasmIPIntPlan.cpp
M Source/JavaScriptCore/wasm/WasmPlan.cpp
M Source/JavaScriptCore/wasm/WasmPlan.h
Log Message:
-----------
[JSC][Wasm] Prefer lowest function index for concurrent CompileError
https://bugs.webkit.org/show_bug.cgi?id=283476
Reviewed by Yusuke Suzuki.
When multiple functions fail validation under concurrent compilation,
keep the error message for the lowest function index instead of
whichever worker finishes first. Function-scoped failures record the
error without completing the plan immediately so later lower-index
failures can replace it. Non-function failures such as OOM are not
replaced by later function errors. EntryPlan stops assigning more work
and ThreadCountHolder completes when active workers drain.
* Source/JavaScriptCore/wasm/WasmPlan.h:
* Source/JavaScriptCore/wasm/WasmPlan.cpp:
* Source/JavaScriptCore/wasm/WasmEntryPlan.h:
* Source/JavaScriptCore/wasm/WasmEntryPlan.cpp:
* Source/JavaScriptCore/wasm/WasmIPIntPlan.cpp:
* JSTests/wasm/stress/consistent-compile-error-function-index.js: Added.
Canonical link: https://commits.webkit.org/319430@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
