Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111301
To: Benjamin Eberlei <kontakt@beberlei.de>,
 PHP Internals <internals@lists.php.net>, Dmitry Stogov <dmitry@zend.com>,
 Nikita Popov <nikita.ppv@gmail.com>
References: <CAEPJdumwKEZymxXGmv-_-NadixnbzyHPVn87NjXzeoGHACtpwQ@mail.gmail.com>
Message-ID: <0e6dff76-0434-4d21-dc08-1fa1bf41a1e0@gmail.com>
Date: Mon, 3 Aug 2020 11:51:43 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0)
 Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <CAEPJdumwKEZymxXGmv-_-NadixnbzyHPVn87NjXzeoGHACtpwQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] @@Jit Attribute Considerations
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> Only the trigger mode 4 (attributes) is actually using @@Jit("tracing") and
> "function". This trigger mode feels like micro-management for developers
> and since it has virtually no spotlight in discussions and blog posts about
> the JIT at the moment, we don't know if it brings benefits.

I think turning JIT off is a valid use case, the rest looks much more
iffy. I am not sure we want to let people tell the engine to JIT certain
functions - are there a lot of cases where the engine wouldn't do it but
it's actually the right thing to do?

Don't see any use for "opcache.jit=attributes".

-- 
Stas Malyshev
smalyshev@gmail.com