Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104001
MIME-Version: 1.0
References: <DM6PR02MB59326E10841277F34E4EFF75BF910@DM6PR02MB5932.namprd02.prod.outlook.com>
 <CAF+90c-Ck7zgU+Z=VX8ewny2s=xrr5RYRC86r_0FJ_gFUM-cmw@mail.gmail.com> <CAFMT4Np9PrrS3uaSMqkrJ8tZd99o-5q51-GeWUGJeQ70zXxxbQ@mail.gmail.com>
In-Reply-To: <CAFMT4Np9PrrS3uaSMqkrJ8tZd99o-5q51-GeWUGJeQ70zXxxbQ@mail.gmail.com>
Date: Sat, 2 Feb 2019 02:29:03 +0700
Message-ID: <CAEZPtU7R0pqE7qfqmYSwLcJ2++h71cSmsJO8AsE94WFHuNG42g@mail.gmail.com>
To: Levi Morrison <levim@php.net>
Cc: Nikita Popov <nikita.ppv@gmail.com>, Dmitry Stogov <dmitry@zend.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000095418f0580da28f2"
Subject: Re: [PHP-DEV] [RFC] JIT
From: pierre.php@gmail.com (Pierre Joye)

--00000000000095418f0580da28f2
Content-Type: text/plain; charset="UTF-8"

On Sat, Feb 2, 2019, 12:46 AM Levi Morrison

I strongly with Nikita's points on cost/benefit analysis. I have
> written a lot but thrown it away because I think this point is so
> important:
>
> It appears that the JIT does not work on Clang or MSVC compilers.


It must some changes needed for php or simply lack of time to test on
MSVC.  LibJit and DynAsm support it

As
> such, I consider this dead on arrival, even if it's considered
> experimental. There are cross-platform JIT's out there -- how do they
> manage it? I think that's the next critical step.
>

--00000000000095418f0580da28f2--