Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 07cae57442c99f84453f39bbca2fcbdc90849ea8
https://github.com/WebKit/WebKit/commit/07cae57442c99f84453f39bbca2fcbdc90849ea8
Author: Yusuke Suzuki <[email protected]>
Date: 2026-06-25 (Thu, 25 Jun 2026)
Changed paths:
M JSTests/stress/arith-abs-to-arith-negate-range-optimizaton.js
M Source/JavaScriptCore/bytecode/CallLinkStatus.h
M Source/JavaScriptCore/dfg/DFGByteCodeParser.cpp
Log Message:
-----------
[JSC] Weakening ByteCodeParser::refineStatically based on some additional
information
https://bugs.webkit.org/show_bug.cgi?id=317716
rdar://180470182
Reviewed by Yijia Huang.
We are observing that this checks are too strong.
1. If callLinkStatus.canOptimize() is false, let's not do anything.
Leave it unknown so that inlining etc. will just ignore that.
We should handle unused callsite as it deserves.
2. From the inlining etc., if we already know that this callsite is
taking function expression from the same code, this is very likely a
closure call. Let's mark it as closure call and avoid using constant
call even if CallIC says so, because it is possible that we are
tiering up too early now.
* JSTests/stress/arith-abs-to-arith-negate-range-optimizaton.js:
* Source/JavaScriptCore/bytecode/CallLinkStatus.h:
* Source/JavaScriptCore/dfg/DFGByteCodeParser.cpp:
(JSC::DFG::ByteCodeParser::refineStatically):
Canonical link: https://commits.webkit.org/315803@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
