Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 963c64aac9edb49bc8d9bdcb72c37603ebb82557
https://github.com/WebKit/WebKit/commit/963c64aac9edb49bc8d9bdcb72c37603ebb82557
Author: Keith Miller <[email protected]>
Date: 2026-06-04 (Thu, 04 Jun 2026)
Changed paths:
M Tools/Scripts/run-jsc-stress-tests
Log Message:
-----------
[JSC] Remove B3O0/O1 test modes from JSC stress tests
https://bugs.webkit.org/show_bug.cgi?id=316324
rdar://178746557
Reviewed by Yusuke Suzuki.
Drop the FTLNoCJITB3O0 (ftl-no-cjit-b3o0) and FTLEagerNoCJITB3O1
(ftl-eager-no-cjit-b3o1) testing modes along with their call sites,
the runLayoutTestFTLEagerNoCJITB3O1 helper, and the now-unused
B3O0_OPTIONS / B3O1_OPTIONS constants. B3-O0 and B3-O1 are no longer
used as part of a normal compiler pipeline, historically they were
used before modern BBQJIT. There is still coverage of O0 and O1 in
testb3.
To preserve coverage of the conservative DFG fallback paths introduced
in 213865@main relocate the two options that uniquely exercised them,
--maxDFGNodesInBasicBlockForPreciseAnalysis=100 and
--useArrayAllocationProfiling=false, into the FTLNoCJITSmallPool mode.
I moved the options to FTLNoCJITSmallPool as it is part of the default
run and is not a graph-validation mode, so the validation modes
continue to exercise the precise (default-threshold) DFG analysis
paths and are not downgraded to the conservative ones, which would
effectively reduce coverage.
Canonical link: https://commits.webkit.org/314570@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
