Re: [RFC] JIT
| From: | Arvids Godjuks | Date: | Fri, 15 Feb 2019 11:09:55 +0000 |
| Subject: | Re: [RFC] JIT | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-104436@lists.php.net to get a copy of this message | ||
пт, 15 февр. 2019 г. в 13:05, Benjamin Eberlei <kontakt@beberlei.de>:
>
>
> On Fri, Feb 15, 2019 at 10:37 AM Dmitry Stogov <dmitry@zend.com> wrote:
>
>> Just two things.
>>
>> I definitely don't think, I "just made it 100x more complicated".
>> I hate complication, and trying to make things simpler and more
>> efficient. This, sometime, involves new more or less isolated subsystems
>> like optimizer and now JIT. Of course, they look complex, if you are not
>> experienced in these areas. But PHP core may work without them.
>>
>> Nobody will port their complex applications to PHP-8 preview, just to
>> try JIT. Having this possibility in PHP-7.4 would involve broader
>> auditory.
>>
>>
> The majority of people uses PHP from pre compiled sources (99%+),
>
> With 7.4 there are just two options:
>
> 1. we add jit as a flag called --enable-experimental-jit - which no
> distribution will do, and you don't have additional exposure with this
> approach.
> 2. or you add it as --enable-jit, and distributions might assume its
> stable and ship it by default, causing potential stability problems.
>
> Both cases are not preferrable to 8.0 master snapshots in my opinion.
>
Well, for production you probably are not gonna use JIT anyway with 7.4, so
not really an issue about distributions. But we have docker, so if there is
a docker image with the JIT - we can use that for testing and local
development.
--
Arvīds Godjuks
+371 26 851 664
arvids.godjuks@gmail.com
Skype: psihius
Telegram: @psihius https://t.me/psihius