Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104218 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 53969 invoked from network); 6 Feb 2019 05:06:18 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 6 Feb 2019 05:06:18 -0000 To: internals@lists.php.net References: <2d85c0cf-fa77-4800-8c4e-cf14a52578ae@SN1NAM02FT010.eop-nam02.prod.protection.outlook.com> <7e128748-e086-e008-f081-2a4ecd24a25d@zend.com> Date: Wed, 6 Feb 2019 02:47:33 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.2 MIME-Version: 1.0 In-Reply-To: <7e128748-e086-e008-f081-2a4ecd24a25d@zend.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 85.230.241.5 Subject: Re: [PHP-DEV] [RFC] JIT From: ajf@ajf.me (Andrea Faulds) Message-ID: Hi, Dmitry Stogov wrote: > > > I've added info from Nikita: PHP-Parser became 1.5 times faster. > That is actually a very good real-world example from my perspective and makes 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 but it's very neglected and pretty useless) and it is exciting if JIT could make PHP do that type of task faster. :) Thanks, Andrea