Re: @@Jit Attribute Considerations

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 >