Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103990
To: internals@lists.php.net
Date: Fri, 01 Feb 2019 10:30:37 -0600
Message-ID: <5896422.hBkj740jAu@vulcan>
In-Reply-To: <4df2d7cf-31dc-a9cf-eefe-d92bad199312@zend.com>
References: <DM6PR02MB59326E10841277F34E4EFF75BF910@DM6PR02MB5932.namprd02.prod.outlook.com> <2321148.uWQDsfDpJu@vulcan> <4df2d7cf-31dc-a9cf-eefe-d92bad199312@zend.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart3495367.1y7v4KasB0"; micalg="pgp-sha512"; protocol="application/pgp-signature"
Subject: Re: [PHP-DEV] [RFC] JIT
From: larry@garfieldtech.com (Larry Garfield)

--nextPart3495367.1y7v4KasB0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Friday, February 1, 2019 2:41:06 AM CST Dmitry Stogov wrote:
> On 2/1/19 3:29 AM, Larry Garfield wrote:

> > Question from a non-compiler-engineer: Could we end up in a situation
> > where
> > future language features (in 8.3 or something) are only performant on JIT-
> > enabled platforms?  I know there were some RFCs rejected in the past on
> > the
> > grounds that they involved too many runtime checks (and thus a performance
> > hit); if it were possible for a JIT to optimize some of those away, it
> > might make the cost acceptable.  However, if a JIT only works on some
> > systems that might widen the gap between have- and have-not platforms.
> 
> I think, JIT only approach doesn't make a lot of sense for PHP, with one
> of the most fast VM. And this is a trend. Even V8, starting from JIT
> only, switched back to VM+JIT.
> 
> Thanks. Dmitry.

I'm... not sure how that answers my question?  I'm saying "if we had a VM+JIT, 
and the JIT part made feature X acceptably fast but it wasn't acceptably fast 
with just the VM, is that a problem?"  Or is that a situation that cannot 
happen?  Or that we don't care if it happens?

--Larry Garfield
--nextPart3495367.1y7v4KasB0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEE/ph/GXfY8v0YwFBp4MMKwDFxYXcFAlxUdC0ACgkQ4MMKwDFx
YXfGDAf+KbHkxWK4lchVVywbz7+Y18baZqKJgRGxVluWlimqN/IWsYVcIfxdZAvk
mq1+1cvBEwdQ6TZnRt9TqAnu5rgPm7yft18C/nUykn3m7tThP8vfP1X1KBpIhpk9
/KHDb6OebJF5Wy7Q+dZD2lGX1lG8Km9HbrZTQi1MQKzvBl3aegEkP2ZDkIqxGpn0
Ub9xlpGTPYShuQX1cFCLu0lOD5xXOGydeDOQvW2J1IJjQP6Vq2n3pUrL6QwcoKMM
Lbu/NHwg3dD5RYcskW6X8iScnJmPmZ1Xsc7raMfCuGdMTPR7jXvJk5iX0Nd3aDfj
UwmXxAZ79nmaUcaG3s2qlRXxcdLr9A==
=NCTr
-----END PGP SIGNATURE-----

--nextPart3495367.1y7v4KasB0--