Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84239 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34065 invoked from network); 3 Mar 2015 14:57:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Mar 2015 14:57:04 -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.182 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 74.125.82.182 mail-we0-f182.google.com Received: from [74.125.82.182] ([74.125.82.182:33370] helo=mail-we0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A0/FB-03783-EBBC5F45 for ; Tue, 03 Mar 2015 09:57:04 -0500 Received: by wevl61 with SMTP id l61so3428786wev.0 for ; Tue, 03 Mar 2015 06:56:59 -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=bhkwHry1UcshCiDCaZnLjcefOmlx5B9wU17ozilrmGA=; b=Vx6QmII2anvZkqBzXPOzbVsm+qej4oPeilrM8fubIWnGKwlMo9IoHYmVBe0qqLku1z wBuJsX8xw1+EP0paxe1WtgIa0Xmps0fP3jBxP+l6Apoii7CMWJy/Z2t4Bdmq5ibzwpz4 sTdxAnLOheMs/KzraWcb+ZNnCP/RVhnE/vGM3TBF8uk8zyEa0gfR68crIDeyUvuo7/ZW bTIINnAL5bMp8GifWoEuCNAyJ4Fy8rpYZJseXfVjpwILzdMZLJ8D5IrFUy3OGpbNwKXI LUWozuvQXDR/bgXgf/sLTEMEoryljc7cluRK8eQbPKFWgHb/pxpPi6KvkXi30VKnGzcy dAuw== X-Gm-Message-State: ALoCoQkkqxTvdxWtTz329a3qck9F98zcr3mf9HICJil9+BnzwbocGz+m1tCS5nCpbtj7vzhBt9+RgaxCrF01zg7ZGZYxSNSRBS0luGNkUHICJu/+auXTwJsIPvqzQSCGy12o1lEQURD23MkHe6q+zq9Jlivs7DSqYg== X-Received: by 10.180.99.34 with SMTP id en2mr3547407wib.81.1425394619441; Tue, 03 Mar 2015 06:56:59 -0800 (PST) References: <246f14640403edad07e8d595fd357286@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQD4C3IYZ8ixidYeCJVBHrwVMMzwcQKM7Vi6APWEoLUCBfYYjQG30wCdAthkrE0CmeEoaAFEPJzrAXfDQG6eP/c/cA== Date: Tue, 3 Mar 2015 16:56:58 +0200 Message-ID: <70f58ecc2ed3df7f3ebf8f45dcc14a42@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: Tuesday, March 03, 2015 4:44 PM > To: Zeev Suraski > Cc: PHP internals > Subject: Re: [PHP-DEV] Re: About optimization for compiler > > I'm looking at https://github.com/zendtech/ZendOptimizerPlus , I cant find > anything related to PHP7 for OPCache. > So I was thinking OPCache was not compatible yet with PHP7. That's the repository for users of old versions (5.5 and earlier). For 7/5.6 it's here: github.com/php/php-src/tree/master/ext/opcache > > 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. > > > > I agree with that as well, just Anthony gave a different opinion which > seems > right as well. I think that if we ever have optimization passes that are prohibitively expensive to run interactively (most probably around JIT) we'll definitely need new strategies for them. But as long as we're talking about relatively optimization passes that take milliseconds to run and not minutes, I think this approach holds true. Zeev