You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Readonly property violations in native JIT code use a second C pending buffer (lib/AOT/runtime/phpc_readonly_raise.c, ~77 lines): __compiler_jit_raise_logic_exception() records the message; AOT mains call phpc_jit_abort_if_pending_logic_exception(). This duplicates the Error pending pattern in phpc_error_raise.c and should live in PHP with a thin ABI.
Category
php-in-phpProblem
Readonly property violations in native JIT code use a second C pending buffer (
lib/AOT/runtime/phpc_readonly_raise.c, ~77 lines):__compiler_jit_raise_logic_exception()records the message; AOT mains callphpc_jit_abort_if_pending_logic_exception(). This duplicates the Error pending pattern inphpc_error_raise.cand should live in PHP with a thin ABI.php-src reference
Zend/zend_object_handlers.c— readonly property write guardsZend/zend_exceptions.c—Errorthrow on modificationRepro (failure today)
Uncaught Error: Cannot modify readonly property R::$xphpc_readonly_raise.c→ PHP throw or AOT stderr fatalScope (this repo)
lib/AOT/runtime/phpc_readonly_raise.c(~77 lines)lib/JIT/ReadonlyBridge.php(or shared pending-exception helper with #5371)lib/JIT/Builtin/Type/Object_.phptest/compliance/cases/language/readonly_jit.phpt(or extend existing readonly suite)Done when
phpc_readonly_raise.cdeleted from tree and linkErrormessage for readonly writeslib/AOT/runtime/./script/ci-fast.sh --filter readonlygreenLinks