Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121235 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 68846 invoked from network); 5 Oct 2023 17:21:11 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 5 Oct 2023 17:21:11 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 2BCA7180503 for ; Thu, 5 Oct 2023 10:21:11 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-ej1-f49.google.com (mail-ej1-f49.google.com [209.85.218.49]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 5 Oct 2023 10:21:07 -0700 (PDT) Received: by mail-ej1-f49.google.com with SMTP id a640c23a62f3a-991c786369cso215539566b.1 for ; Thu, 05 Oct 2023 10:21:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696526466; x=1697131266; darn=lists.php.net; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=IEVvkXRYrdFJKT4sl2YUJABGqM9uG+bkYUYESH9soAM=; b=JIJ7u210ZcFyKTyQEQ9mqcYtspcuZdZa3I7Yvg3kTixLUVBLH7x2Ox5MOD2ZRaSpqh fORB0WufEkReENFCkWsZyS7qd3X4IVXs3bqp19vP00kb6VA5gYbGfOgZsKBorviE+F1G 1SDLX/DO6iGV1ZckVhYptHIgeJpqsens4VSNorhVukukAnEAzXozYeMcPu/GTjFvO0yJ p66g5YndSY25tqey+S6gv3izm4IBYDHb13dYoKbwjXcE34ln0xHFYsBsneU9e6evYYaH xA8kDO2ELJnlcChAirP8ZQqGSMeGEf1WybzY2AkPWaVoR7w7eojXlpSHFL0SRSpydKdZ qTYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696526466; x=1697131266; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=IEVvkXRYrdFJKT4sl2YUJABGqM9uG+bkYUYESH9soAM=; b=Kec5B62XCe9WF0lS3F9J4/Mi+KItAlqFMRyZ7q83VT6rW/TQ6OBjIHOokil1mfMWf/ iH+ek5deVw0gKawUAps9gqi061GbtgbndSc8aZBPzboAIZSW6Xom2itiiiO6Vpy5f3CU b1roj//vgrcgGEz+jzler9ZMPmLExshUAd58skrnOoXQ13OZ/SNkDbFJmcfs2rWohFx1 UkAnlvjq+mTGy7NOd82wJjtrOeyMxuLEi3BL0ElKg6GwGCufDxFSzY8Low+LVxdVRNio zU9F37AF+y1MuD1nTx9QLYb77lVrFQ+hL6jJ6830Hh0aEmWXmDh61DBwQGyUp/STWwrs 0yOg== X-Gm-Message-State: AOJu0YzzIQxkFLYCzQwk5ueYNZNzd3jfI7m7ZHeyzTOSW1DOpwK/dXoB TrEJgmlmrdohh7e9r+QBxi5aUGkL3LLaIaF/2mIgjmkJ X-Google-Smtp-Source: AGHT+IEy5UGFLgXXz0DMCtbYhLzvLxQv8C1iKMythTC73HpO5RCnjo6J/QBlU5NPZmNqN6GUx65i91Q4eSLUnpVr0jA= X-Received: by 2002:a17:906:19b:b0:9b6:e6ff:b20b with SMTP id 27-20020a170906019b00b009b6e6ffb20bmr4977535ejb.8.1696526465932; Thu, 05 Oct 2023 10:21:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 5 Oct 2023 18:20:54 +0100 Message-ID: To: Dmitry Stogov Cc: PHP Internals Content-Type: multipart/alternative; boundary="0000000000005aa1e20606fb598f" Subject: Re: [PHP-DEV] [RFC] [Discussion] A new JIT implementation based on IR Framework From: dragoonis@gmail.com (Paul Dragoonis) --0000000000005aa1e20606fb598f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 5 Oct 2023, 17:44 Dmitry Stogov, wrote: > Hi Internals, > > I've published a presentation about the IR Framework design and > implementation details. > See > > https://www.researchgate.net/publication/374470404_IR_JIT_Framework_a_bas= e_for_the_next_generation_JIT_for_PHP > It explains many complex things in simple pictures. > Hi Dmitry, Thanks for helping explain things in graphical format. I will for sure study the material closely. As for the point around keeping the old JIT around as a safety measure and fallback. I think this is an excellent idea and may give good peace of mind and confidence for new adopters, that they can easily "switch back" to JIT 1.0 if any edge cases occur we didn't find yet in JIT 2.0, without waiting for future PHP releases (patches) to come out. It can be months before people get new patched PHP versions (think about centos or Debian distributions, or Docker images of PHP) Just like we've done with many things over the years, we first deprecated something and keep it in the language and in future release we remove it completely. Many thanks, Paul > Thanks. Dmitry. > > On Thu, Sep 21, 2023 at 11:26=E2=80=AFAM Dmitry Stogov > wrote: > > > Hi Internals, > > > > After all the Poll Request discussions (see > > https://github.com/php/php-src/pull/12079), code-reviews and internal > > discussions with core developers we decided to move this through the RF= C > > process. > > > > Thanks to all participants. > > > > The RFC is open for discussion: https://wiki.php.net/rfc/jit-ir > > > > Thanks. Dmitry. > > > --0000000000005aa1e20606fb598f--