Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84236 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26855 invoked from network); 3 Mar 2015 13:52:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Mar 2015 13:52:23 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 74.125.82.169 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 74.125.82.169 mail-we0-f169.google.com Received: from [74.125.82.169] ([74.125.82.169:37814] helo=mail-we0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1A/BA-03783-69CB5F45 for ; Tue, 03 Mar 2015 08:52:23 -0500 Received: by wesw55 with SMTP id w55so39941620wes.4 for ; Tue, 03 Mar 2015 05:52:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=JiMe5D5QdJPyzXkLi7qN01/j624u1j3wkSO4LClob+U=; b=e0ObgFFBCZeyWutJueCmLqJdsB878FGmE48gabaLyY1To/Vt8jO90j7LV1MVtq2u3j 2FQSGfVDUFMjaDxqtFYLMDkqgAtjToiYfWlHm4dGoNKB6yhG0+wnn2BGV/+I+7sPEIeu LX2druy3Gtk++433J9d24G6hoB5TI2aaJ/SPaCXzpYb/mHV0ZMXkWeoxnT/8/lSx1zcJ /KYg5TSgrp5Yc1rWohKtWMWbuQ5/Q9eUyskDnDGcKS9K2vP7K3joONKepogOUHV5s7x2 VfdqDEp5PBkzsfOti9H4RSUWciTKR0E93YxBnT+x4urzR0B+ejy5GYAKEcY3Yfyr6xL7 c+Jg== X-Gm-Message-State: ALoCoQk6glexQ1Az5hgr+zrZFpeCB3DQqXBED5cldx8Ow1fjGSyPTDQy0SQz+wNq8/OLP6nl0OO/vKCc6u425CsipFIvSQuPZyYz3fF7Ctm/+yRemXwWusDVGndx7wVC7syE7xmJzcwryAzo/toUMzXb/mSpjOssIQ== X-Received: by 10.194.63.172 with SMTP id h12mr68171898wjs.48.1425390739538; Tue, 03 Mar 2015 05:52:19 -0800 (PST) References: In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQD4C3IYZ8ixidYeCJVBHrwVMMzwcQKM7Vi6APWEoLUCBfYYjQG30wCdAthkrE0CmeEoaJ5VxNzg Date: Tue, 3 Mar 2015 15:52:18 +0200 Message-ID: <246f14640403edad07e8d595fd357286@mail.gmail.com> To: Julien Pauli Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Subject: RE: [PHP-DEV] Re: About optimization for compiler From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: julienpauli@gmail.com [mailto:julienpauli@gmail.com] On Behalf Of > Julien Pauli > Sent: Monday, March 02, 2015 9:07 PM > To: Dmitry Stogov > Cc: Bob Weinand; Xinchen Hui; PHP Internals > Subject: Re: [PHP-DEV] Re: About optimization for compiler > > As OPCache is nowadays not compatible at all with PHP7 (development has > not started yet, or I'm not aware of it) , why not merge OPCache to PHP7 > source tree (when the time for this will come), still as an extension at > first > time, and keep developing optimizer passes into this (aka : not in Zend/) > ? It's a bit OT, but can you explain what you mean here? OPcache works with the current master (PHP 7), and actually, OPcache worked with phpng all along and definitely since it was merged into master... It's been integrated to the php-src tree since it became standard in 5.5. Do you mean the standalone github repos for older versions? > I'm also +1 to keep our optimizations into OPCache (into an extension), I'm slightly confused - you mean keep it in (or move optimization over to) the OPcache extension, or move it into its own extension? If it's the former, then I agree. Optimization passes and opcode caching are very much linked, as performing optimizations without having an opcode cache rarely makes sense. > and > allow them to be disabled (like its the case actually), because this > subject is > very hot and sensible. > > We should keep a PHP compiler as-is, and move optimization passes away > from it. zend_extension_op_array_handler() callback is designed for that > purpose. Agreed. Zeev