Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121086
MIME-Version: 1.0
References: <CAPVMwwtcLwq8AGEBYCXB1-HngS1R0D-xM5kTGjYqEdjmB7M=ag@mail.gmail.com>
 <CAPVMwwu9+RK13ByqFpexrQ4Sc+xARvyQb=WVxruhVtGKzxjo+A@mail.gmail.com>
 <8b9a1aae-5aec-91a8-5377-27f6f53581cd@php.net> <65047d5b.810a0220.1c748.455bSMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <65047d5b.810a0220.1c748.455bSMTPIN_ADDED_MISSING@mx.google.com>
Date: Mon, 18 Sep 2023 09:36:17 +0300
Message-ID: <CAPVMwwvnG=A1RN3qe7AceWHPMcc+gwkEDB5RgOg9=u8mk-EvFQ@mail.gmail.com>
To: Ben Ramsey <ramsey@php.net>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000b7a20d06059c5c0d"
Subject: Re: [PHP-DEV] A new JIT engine for PHP-8.4/9
From: dmitrystogov@gmail.com (Dmitry Stogov)

--000000000000b7a20d06059c5c0d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Ben,

On Fri, Sep 15, 2023 at 6:50=E2=80=AFPM Ben Ramsey <ramsey@php.net> wrote:

> On 9/15/23 09:35, Derick Rethans wrote:
>
> > I understand that working on an RFC for such a complex issue is going t=
o
> > take time, but that also gives to opportunity to pair with somebody,
> > who, while writing it, will also learn how it works. That would also
> > ready improve the debugging/contributing issues.
>
> +1, this needs an RFC, if only to help articulate and explain how it
> works, as Derick says. I'd love to volunteer to help with the RFC, but
> I'm already stretched thin, as it is.
>

As I said, I'm going to publish a presentation (in October).
I'm not sure if we should have an RFC that will repeat it.
Anyway, if you like to understand how PHP-JIT-IR works and explain this to
others, I would appreciate this.
I'm ready to answer any questions.


> A few things I noted while looking through the code in the IR repository.=
..
>
> It looks like the goal of the project is for IR to provide JIT
> compilation for other projects. Do you already have some idea where
> (other than php-src) it will be used? Is it already being used elsewhere?
>

Pierre thinks about WASM backend.
I like to write a C front-end and something similar to Truffle.


> IR is currently on your personal GitHub account, but the copyright
> listed on the license is for "Zend by Perforce," while other source
> files (e.g., ir_cpuinfo.c) list "IR project" as the copyright holder. I
> assume this is because you (Dmitry) have been working on this on Zend's
> time, while other contributors have been working on it independently.
> Who is the ultimate owner/controller of the project? If it's a Zend by
> Perforce project, what's their goal for it? (I'm not asking because I
> think there are hidden agendas; I'm just curious what the plans are for
> long-ish term support of IR.)
>
> Noted that the license on IR is MIT. Love it!
>

The IR project was developed under the  "Zend by Perforce" umbrella.
It paid for development, it has the copyright, but we choose the most
permissive license.
The main goal is the improvement of PHP, but we also like to involve
non-PHP experts.

Thanks. Dmitry.

--000000000000b7a20d06059c5c0d--