[php-src] Issue #20458: Ability to whitelist/blacklist functions from JIT
| From: | dktapps | Date: | Wed, 12 Nov 2025 00:04:29 +0000 |
| Subject: | [php-src] Issue #20458: Ability to whitelist/blacklist functions from JIT | ||
| Groups: | php.bugs | ||
| Request: | Send a blank email to php-bugs+get-251207@lists.php.net to get a copy of this message | ||
Issue: https://github.com/php/php-src/issues/20458
Author: dktapps
### Description
I maintain a decent size, long-running [application](https://github.com/pmmp/PocketMine-MP) using
PHP.
I've been very excited about the introduction of JIT into PHP before, since as a long-running,
CPU-heavy application, it stands to benefit far more from JIT than the average PHP application.
However, our attempts to rollout JIT usage have been constantly thwarted by a plague of crashes and
stability issues that have made it unusable for all practical purposes. This remains true as of PHP
8.4, although I will grant that the stability of the JIT does seem a lot better since the
introduction of IR.
This issue is a request for some way to whitelist/blacklist code from being JITed.
For example, there is some math-heavy code in PocketMine that benefits from tracing JIT to the tune
of a 5x performance improvement. It would be a probably acceptable tradeoff to enable JIT in just
that one code pathway to get that huge performance improvement, since we can test that specific part
of the code heavily in isolation, while avoiding it in other areas where stability is more
important.
Conversely, it would make it much easier to track down JIT issues in large applications if there
were some way to blacklist code from being compiled by the JIT.
Perhaps this could take the form of
#[AllowJIT] and/or #[DenyJIT]
attributes on functions, but maybe there is a better way that I'm not aware of.