Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104221
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
In-Reply-To: <5c5a3cc8.1c69fb81.a043e.7adcSMTPIN_ADDED_MISSING@mx.google.com>
Date: Wed, 6 Feb 2019 01:03:40 -0500
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <4AAB6056-78AF-4D43-947F-2F249E7852FF@gmail.com>
References: <DM6PR02MB59326E10841277F34E4EFF75BF910@DM6PR02MB5932.namprd02.prod.outlook.com> <2d85c0cf-fa77-4800-8c4e-cf14a52578ae@SN1NAM02FT010.eop-nam02.prod.protection.outlook.com> <7e128748-e086-e008-f081-2a4ecd24a25d@zend.com> <5c5a3cc8.1c69fb81.a043e.7adcSMTPIN_ADDED_MISSING@mx.google.com>
To: Andrea Faulds <ajf@ajf.me>
Subject: Re: [PHP-DEV] [RFC] JIT
From: matthewmatthew@gmail.com (Matthew Brown)

I=E2=80=99m not sure it=E2=80=99s a great real-world example - PHP Parser is=
 much more maths-y than the vast amount of PHP code, but if your PHP-based c=
ompiler had a similar makeup it might show somewhat similar benefits.

> On Feb 5, 2019, at 8:47 PM, Andrea Faulds <ajf@ajf.me> wrote:
>=20
> Hi,
>=20
> Dmitry Stogov wrote:
>> I've added info from Nikita: PHP-Parser became 1.5 times faster.
>=20
> That is actually a very good real-world example from my perspective and ma=
kes a better case for why JIT compilation to native code would be beneficial=
. I would like to write a PHP compiler in PHP (actually, I began doing so bu=
t it's very neglected and pretty useless) and it is exciting if JIT could ma=
ke PHP do that type of task faster. :)
>=20
> Thanks,
> Andrea
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20