Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83959
Return-Path: <laruence@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 73846 invoked from network); 27 Feb 2015 06:27:03 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 27 Feb 2015 06:27:03 -0000
Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.50 as permitted sender)
X-PHP-List-Original-Sender: laruence@gmail.com
X-Host-Fingerprint: 209.85.215.50 mail-la0-f50.google.com  
Received: from [209.85.215.50] ([209.85.215.50:39325] helo=mail-la0-f50.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 6E/50-32582-63E00F45 for <internals@lists.php.net>; Fri, 27 Feb 2015 01:27:03 -0500
Received: by labgq15 with SMTP id gq15so15598114lab.6
        for <internals@lists.php.net>; Thu, 26 Feb 2015 22:27:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=qrmVrGrRzVOHObT/QVz/G0TSCDy5bfs6yYgqF8jw/24=;
        b=Hg6O77ml8uKoaVnIfcg7y3sUvEiKFGju1cyQ+69XxeEZK3Lz1sBunYplxvuNQRBTg6
         XqrXwEAfdWfYn+NEUBXTrjvJFesZnXA8RR0pQ/1LuHRKDTvuv7bTyMARa5jnJyImkjec
         41U8N0OGA6Dmw97r/mNpLllT8nFEKzORYIkaQsmSwgUMJ6sUtQR4zPR5gJgQ22tYGPcr
         Qrtjx1kjUIWLXtP5sl5igMloGT3R9hGa8qqgbQcrGp3J954qA00OGxtJQkjJ0M3mV7Ib
         CzR1lnFGsXiH+xCYTAa8nedQBnHaqDM6orrHYOEArgUe/kE1CUxfl1XlMZKfsDSrm2Xq
         hW4g==
X-Received: by 10.152.115.136 with SMTP id jo8mr11359074lab.32.1425018420269;
 Thu, 26 Feb 2015 22:27:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.114.28.198 with HTTP; Thu, 26 Feb 2015 22:26:40 -0800 (PST)
In-Reply-To: <CABBJUpd8f8ApcPqJp6d5ih0Bywkk4LUnFdQOD=ovL1U6nhid0Q@mail.gmail.com>
References: <CABBJUpd8f8ApcPqJp6d5ih0Bywkk4LUnFdQOD=ovL1U6nhid0Q@mail.gmail.com>
Date: Fri, 27 Feb 2015 14:26:40 +0800
Message-ID: <CABBJUpcgO3Ns8hDqRkTN0AMaUjVZdi7yzWiDDEX4OXPj2QCsuw@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>, Dmitry Stogov <dmitry@zend.com>, 
	Bob Weinand <bobwei9@hotmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: About optimization for compiler
From: laruence@gmail.com (Xinchen Hui)

Hey:

On Fri, Feb 27, 2015 at 2:22 PM, Xinchen Hui <laruence@gmail.com> wrote:
> Hey Internals:
>
>       I was looking Bob's switch optimization..
>
>       then I start to worry about where is the place optimization should goes..
>
>       in generally, PHP is a  interpreted language. IMO, it should
> compiler the PHP codes to opcode without any optimization(of course,
> we did some, but they won't change a lots of opcodes which should be
> generated)..
>
>       and, since 5.5, we already have opcache bundled in..
>
>       thus, I am proposing a principle, that is:
>
>       in the future, we only do optimization in opcache side, and keep
or maybe big optimization?  but I don't know how to define "big" or
"small" optimizations now..

(small is the optimizations, we are sure it is safe, maybe)

thanks
> Zend Compiler without any optimization... considering Zend Compiler do
> things in -O0.
>
>       since, optimization always are dangerous.. if we only do them in
> opcache, user can still run them codes with disable opcache, or at
> least disable some optimization level which cause that..
>
>       what do you think?
>
> thanks
>
> --
> Xinchen Hui
> @Laruence
> http://www.laruence.com/



-- 
Xinchen Hui
@Laruence
http://www.laruence.com/