Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104233
MIME-Version: 1.0
References: <DM6PR02MB59326E10841277F34E4EFF75BF910@DM6PR02MB5932.namprd02.prod.outlook.com>
 <2321148.uWQDsfDpJu@vulcan> <4df2d7cf-31dc-a9cf-eefe-d92bad199312@zend.com>
 <5896422.hBkj740jAu@vulcan> <67097B20-5D7D-489E-8C5B-E238890A7A83@zend.com>
 <qped5eh4mles7ghevmmo4cud1gd7i8c2nd@4ax.com> <D1D0DAB5-4FE6-44BB-B78C-FB53C1552977@zend.com>
 <f8vd5epda8hv2laemsun51iau5buohdnbj@4ax.com> <A49A57E5-A785-4E26-8986-59AA90202BCC@gmail.com>
 <CAF+90c95Ptn8-vVMyc4MLLfHVt12L9vW8Nyu4+Cb+R4Q5HtLHA@mail.gmail.com> <5203a083-4932-b564-1f23-6a4eb2f9fe8c@zend.com>
In-Reply-To: <5203a083-4932-b564-1f23-6a4eb2f9fe8c@zend.com>
Date: Wed, 6 Feb 2019 10:26:40 +0100
Message-ID: <CAF+90c_msurQ40M2xEx=mpeXokiRzxMV+V+JLjzJsDTti=v71Q@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: Zeev Suraski <vsuraski@gmail.com>, Jan Ehrhardt <phpdev@ehrhardt.nl>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e29ee50581365339"
Subject: Re: [PHP-DEV] [RFC] JIT
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000e29ee50581365339
Content-Type: text/plain; charset="UTF-8"

On Mon, Feb 4, 2019 at 8:30 AM Dmitry Stogov <dmitry@zend.com> wrote:

>
>
> On 2/3/19 9:00 PM, Nikita Popov wrote:
> > On Sun, Feb 3, 2019 at 5:16 PM Zeev Suraski <vsuraski@gmail.com> wrote:
> >
> >>
> >>> On 3 Feb 2019, at 16:43, Jan Ehrhardt <phpdev@ehrhardt.nl> wrote:
> >>>
> >>> Zeev Suraski in php.internals (Sun, 3 Feb 2019 11:02:56 +0000):
> >>>>
> >>>>
> >>>> How is that related?
> >>>
> >>> It is directly related with your statement that "developers with other
> >>> host OSs still use Linux for the actual PHP development". They don't
> use
> >>> Linux for the actual PHP development. They are using Windows.
> >>
> >> That statement was in a certain context - for those who use containers
> and
> >> Linux VMs, which is (as mentioned) a growing trend.  I think it's clear
> >> that I'm not claiming it's everyone, or even the majority - but if it
> >> wasn't clear - it should be now...
> >>
> >> Zeev
> >>
> >
> > I feel like this discussion ended up going a bit astray, with a focus on
> > only the issue of Windows support... While I think that we should
> endeavor
> > to support at least Windows and MacOS before the JIT hits a release
> version
> > of PHP, at this point in time (and for the purposes of the vote) the
> > questions of maintenance and stability are the most important.
>
> If we don't start, we definitively won't get support.
>
>
> > Ultimately
> > those questions can't really be answered until interested parties have
> > reviewed the JIT codebase. To that end it would be helpful if:
> >
> > a) A PR of the JIT branch could be submitted against php-src, so there
> is a
> > place for review comments and more technical discussions. (It might be
> > necessary to squash, as GH doesn't deal with large history well.)
>
> OK. Not sure about re-base.
>
> > b) The RFC (or some other place) is extended with some high-level design
> > information on how the JIT works on a technical level. Some notes on how
> > JIT bugs are usually debugged would also be very helpful.
>
>
> OK. I'll try to extend RFC with some design elements.
>
> Thanks. Dmitry.
>

As you probably spent a lot of time profiling the JIT, I'm wondering if you
have any insights about what the main issues are right now that prevent
better performance and what some idea to improve those would be. E.g. I
don't think the JIT currently does any inlining (right?) and that might be
something that could give a benefit?

Nikita

--000000000000e29ee50581365339--