Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111982 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 71668 invoked from network); 2 Oct 2020 10:46:57 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 2 Oct 2020 10:46:57 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 75D8E180087 for ; Fri, 2 Oct 2020 02:59:19 -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=-1.5 required=5.0 tests=BAYES_00,KHOP_HELO_FCRDNS, SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from processus.org (ns366368.ip-94-23-14.eu [94.23.14.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 2 Oct 2020 02:59:18 -0700 (PDT) Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by processus.org (Postfix) with ESMTPA id CE51AC34F9; Fri, 2 Oct 2020 09:59:16 +0000 (UTC) To: Levi Morrison , Dik Takken Cc: Nikita Popov , Rowan Tommins , PHP internals References: <940131FA-19B3-406C-8982-0AD276FD1879@gmail.com> <142da816-f3bf-2f05-6147-ccd2117e1dfd@gmail.com> Message-ID: Date: Fri, 2 Oct 2020 11:59:15 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US Authentication-Results: processus.org; auth=pass smtp.auth=pierre-php@processus.org smtp.mailfrom=pierre-php@processus.org X-Spamd-Bar: / Subject: Re: [PHP-DEV] RFC: execution opcode file without php source code file From: pierre-php@processus.org (Pierre) Le 01/10/2020 à 18:32, Levi Morrison via internals a écrit : > Note that for PHP 8.0 we made the system ID change even more than it > used to because doing so fixes sigsegvs when switching what extensions > are loaded (common when trialing an APM product, or loading and > unloading xdebug) when file cache is used. This means that it is even > more important to have sources than in the past, and necessarily so > because of real segmentation faults. > > So I second Nikita's opinion: this is not going to work well without > stabilizing the opcode format. This may be possible, but it would be a > lot of work; it's not happening soon. If you do it anyway be prepared > for plenty of crash complaints. > Hello, I know this may sound naive, but would it be a bad idea to stabilize opcodes (which probably is much harder than it looks), having the VM being built following a thorough specification ? I could open the door to many things, such as third party compilers or optimizers ? I don't know much Zend VM internals, but having the possibility to have PHP binaries other than phar sound compelling to me, I wish I could deliver upgrades using a single binary instead of a 100k PHP files delivery, especially in docker environments. It may also open the door to autoload-less execution, link time-like optimizations, and even open a slight door toward reflection around modules/packages ? Regards, Pierre