Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: a4c33dfcff8daf9dfeca62687d7d5a4b0749f127
https://github.com/WebKit/WebKit/commit/a4c33dfcff8daf9dfeca62687d7d5a4b0749f127
Author: Keith Miller <[email protected]>
Date: 2026-02-17 (Tue, 17 Feb 2026)
Changed paths:
M Source/JavaScriptCore/bytecode/InlineCacheCompiler.cpp
Log Message:
-----------
[JSC] Getter ICs shouldn't check for NullSetterFunction
https://bugs.webkit.org/show_bug.cgi?id=308063
rdar://170563020
Reviewed by Yusuke Suzuki.
It's not possible to get a NullSetterFunction as a get function in JS so
checking for it in the IC code is presumably a mistake (probably from a
refactor). I assume NullGetterFunction is also sufficiently rare that it
no longer makes sense to preemptively branch on it. Naively, there's not
a lot of use cases for a property that can't be read, so optimizing for
it doesn't seem worthwhile.
No new tests, covered by existing tests.
Canonical link: https://commits.webkit.org/307725@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
