Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129402
Date: Sat, 22 Nov 2025 21:51:06 +0000
To: Arnaud Le Blanc <arnaud.lb@gmail.com>
Cc: Brent Roose <brent.roose@jetbrains.com>, PHP Internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] What's the status of the JIT?
Message-ID: <kAvd1I1i2si5dOZvwWARKVUjw3XASXs1UqAPCPcl8C90ToMb_QHqXd-mkapDEY4Rk5-3k_E_AaOBHEnG3nQC4X-veFdrkQl562X7wb9xDgE=@gpb.moe>
In-Reply-To: <CAP1Jc10GXcH0D=jO0_+sKV7A8V2mJHwL28TQQDCE0F9L5+w-NQ@mail.gmail.com>
References: <CANSNCr2JXXmLnNqSxVXQM7i3j_WBi3jmznM4-_rd34LDkmvLZg@mail.gmail.com> <CAP1Jc10GXcH0D=jO0_+sKV7A8V2mJHwL28TQQDCE0F9L5+w-NQ@mail.gmail.com>
Feedback-ID: 96993444:user:proton
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: internals@gpb.moe ("Gina P. Banyard")

On Friday, 21 November 2025 at 15:25, Arnaud Le Blanc <arnaud.lb@gmail.com>=
 wrote:

> Regarding the impact of the JIT on internal development, I believe
> that it's relatively low:
>=20
> * The JIT is known to be a bit unstable yet, and there are occasional
> JIT bug reports, but these affect only the JIT and deployments with
> JIT enabled
> * Changes to the VM are likely to require changes to the JIT as well,
> but this is not the majority of the work
> * Language changes, such as those proposed in RFCs, often require JIT
> changes as well. But RFCs are not required to implement JIT changes
> before voting, so this only adds overhead on accepted RFCs. This
> represents a very small fraction of the work required on an RFC.
> * Other changes don't usually need to care about the JIT
>=20
> Best Regards,
> Arnaud

To expand on this, the only times I really need to touch the JIT is when pr=
oposing language deprecations.
Even when working on the Container/Offset RFC, the tweaking of the JIT was =
relatively straight-forward.


Best regards,

Gina P. Banyard