Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83962
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAG1choqG519Fpoo3s=pxmOGw2rR94VdqrXMsE7XbefecyTQ4FA@mail.gmail.com>
References: <CABBJUpd8f8ApcPqJp6d5ih0Bywkk4LUnFdQOD=ovL1U6nhid0Q@mail.gmail.com>
 <CABBJUpcgO3Ns8hDqRkTN0AMaUjVZdi7yzWiDDEX4OXPj2QCsuw@mail.gmail.com> <CAG1choqG519Fpoo3s=pxmOGw2rR94VdqrXMsE7XbefecyTQ4FA@mail.gmail.com>
Date: Fri, 27 Feb 2015 14:49:30 +0800
Message-ID: <CABBJUpdsniOo=dMB8b=HOuUGftq6dMut2zjoyrYKPxT59M_63A@mail.gmail.com>
To: reeze <reeze@php.net>
Cc: 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: [PHP-DEV] Re: About optimization for compiler
From: laruence@gmail.com (Xinchen Hui)

Hey:

On Fri, Feb 27, 2015 at 2:41 PM, reeze <reeze@php.net> wrote:
> Hi,
>
> On 27 February 2015 at 14:26, Xinchen Hui <laruence@gmail.com> wrote:
>>
>> 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?
>
>
> We may need to clarify which kind of optimizations we want to set a
> principle.
> There are different level's optimizations.
>
> Opcache is a opcode to opcode optimizer, but some optimizations might need
> lower level
> optimizations like Bob's, some might need to change base data structure.
>
> We have AST intermediate represent structure, there might  be some AST level
> optimizations,  this not opcache's job too.
maybe you misunderstand , but let me declare it again.

that's what I proposed.. keep opcodes honestly represents what php
codes is... (stop doing optimization for compiler for now, and
introduces APIs for optimizations, then do them outside of Zend)

thanks
>
>>
>> >
>> > thanks
>> >
>> > --
>> > Xinchen Hui
>> > @Laruence
>> > http://www.laruence.com/
>>
>>
>>
>> --
>> Xinchen Hui
>> @Laruence
>> http://www.laruence.com/
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>
>
>
> --
> Reeze Xia
> http://reeze.cn



-- 
Xinchen Hui
@Laruence
http://www.laruence.com/