Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111302
MIME-Version: 1.0
References: <CAEPJdumwKEZymxXGmv-_-NadixnbzyHPVn87NjXzeoGHACtpwQ@mail.gmail.com>
 <0e6dff76-0434-4d21-dc08-1fa1bf41a1e0@gmail.com>
In-Reply-To: <0e6dff76-0434-4d21-dc08-1fa1bf41a1e0@gmail.com>
Date: Mon, 3 Aug 2020 21:20:35 +0200
Message-ID: <CAEPJdu=Cgwf4SM5g8QkKRH0mAd-v5cBEwVOMx4CO7R40cJ+P_A@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP Internals <internals@lists.php.net>, Dmitry Stogov <dmitry@zend.com>, 
	Nikita Popov <nikita.ppv@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000001c0c9405abfe0979"
Subject: Re: [PHP-DEV] @@Jit Attribute Considerations
From: kontakt@beberlei.de (Benjamin Eberlei)

--0000000000001c0c9405abfe0979
Content-Type: text/plain; charset="UTF-8"

On Mon, Aug 3, 2020 at 8:51 PM Stanislav Malyshev <smalyshev@gmail.com>
wrote:

> 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?
>

In that case maybe we should rename the attribute to @@DisableJit ? This
would not clutter the global namespace with a "jit" class.

>
> Don't see any use for "opcache.jit=attributes".
>
> --
> Stas Malyshev
> smalyshev@gmail.com
>

--0000000000001c0c9405abfe0979--