Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109627
To: internals@lists.php.net
Reply-To: internals@lists.php.net
Message-ID: <0ddd2987-644b-6fec-2670-2b6f366290e2@php.net>
Date: Tue, 14 Apr 2020 15:53:31 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: opcache.jit directive should be split up
From: sebastian@php.net (Sebastian Bergmann)

PHP 8's JIT is currently mainly controlled through the opcache.jit 
configuration directive [1].

The value for opcache.jit is currently a sequence of four digits, "5021" 
for instance. This would activate JIT optimizations based on static type 
inference and inner procedure analyses (Optimization Level), JIT 
optimization of all functions on load of the respective sourcecode file 
(Trigger), global linear-scan register allocator (Register Allocation), 
and AVX instruction generation (CPU-Specific Optimization Flags).

I think that using a single configuration directive for these four 
distinct aspects of just-in-compilation is a bad idea. Many will, at least 
at first glance, mistake the value for a bitmask.

I think it would be best to split up opcache.jit into five separate 
configuration directives and propose the following names:

* opcache.jit for (de)activating JIT
* opcache.jit_optimization_level for setting the optimization level
* opcache.jit_trigger for configuring the JIT trigger
* opcache.jit_register_allocation for configuring register allocation
* opcache.jit_cpu_flags for configuring CPU-specific flags

What do you think?

-- 
[1] https://wiki.php.net/rfc/jit#phpini_defaults