Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44195
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain facebook.com designates 69.63.179.25 as permitted sender)
To: Paul Biggar <paul.biggar@gmail.com>, Nuno Lopes <nlopess@php.net>
CC: PHP Internals <internals@lists.php.net>, Brian Shire <shire@facebook.com>
Date: Sat, 6 Jun 2009 18:52:25 -0700
Thread-Topic: [PHP-DEV] RE: Optimizer discussion
Thread-Index: AcnnD1s94mRhARInS6+8R55s8HqvegAAz99l
Message-ID: <DEA757D29DE3314393C26D2EA705A7E736095A91B1@SC-MBXC1.TheFacebook.com>
References: <af54caaf0906041620o1de77e2br10d1d80ef0130192@mail.gmail.com>
 	<DEA757D29DE3314393C26D2EA705A7E73605C1B34B@SC-MBXC1.TheFacebook.com>
 	<E6C35D22F6874DCD96473EEF91D0BABD@PC3EE1F19287>,<af54caaf0906061828i651d4a5ax3e9242c25e5cb240@mail.gmail.com>
In-Reply-To: <af54caaf0906061828i651d4a5ax3e9242c25e5cb240@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: RE: [PHP-DEV] RE: Optimizer discussion
From: grahamk@facebook.com (Graham Kelly)

Hey,

Sorry I haven't replied sooner. I'm glad to see that there is some interest=
 here. :-)

Basically where I am at with the project at the moment is trying to get 5.3=
 compatibility with the current optimizer. At which point I would like to m=
ore or less dump the code base I have now in favor of starting from the gro=
und up on something that can be built into a much more powerful system. I d=
o really like your idea Paul about using eval or something similar for doin=
g compile time evaluations. Hopefully I can implement many of the stuff (li=
ke all the function optimizations) this way. That should help to reduce a L=
OT of the duplicated code; which I agree is not a good thing to have. I've =
been working on whipping up an outline of where I want to take the project.=
 I look forward to getting feedback on that :-).

As for runkit, I am not overly concerned with compatibility for extensions =
such as runkit or xdebug, etc at the moment. I don't really see this being =
too big of an issue for many people and if it turns out to be one I can loo=
k into it when the time comes.

Also, I wanted to let you know that I really enjoyed your tech talk, Paul. =
Your papers also seem like really interesting (from what I have read thus f=
ar).

- Graham

________________________________________
From: Paul Biggar [paul.biggar@gmail.com]
Sent: Saturday, June 06, 2009 6:28 PM
To: Nuno Lopes
Cc: Graham Kelly; PHP Internals; Brian Shire
Subject: Re: [PHP-DEV] RE: Optimizer discussion

On Fri, Jun 5, 2009 at 11:23 PM, Nuno Lopes<nlopess@php.net> wrote:
> I'm happy there's some interest in a PHP optimizer :)
> I agree with Paul that PECL's optimizer duplicates way too much stuff fro=
m
> the Zend engine, which is not practic nor maintainable. (compare for exam=
ple
> with the simple constant folder I implemented some years ago:
> http://web.ist.utl.pt/nuno.lopes/zend_constant_folding.txt).

This is certainly a much better demonstration of how the optimizer should w=
ork.

> About runkit & friends, I wouldn't worr
 much about them. If you're running
> them problably you also don't care about optimizations. If you want to be
> able to optimize something, you need to remove as many freedom degrees as
> you can..

This is probably true of runkit. However, I would be careful what you
remove for extra freedom. There is very likely PHP code out there that
relies (possibly by accident) on some edge cases.


> P.S.: I'll try to meet with Paul in PLDI (in a week) and chat about these
> kinds of things. Is anyone else comming that wants to join the discussion=
?

You should probably mention this is in Dublin.

Some of the IBM Toyko researches who work on (or maybe close to)
Project Zero will be there, and might have interesting ideas. They
have a paper on PHP memory usage.



Paul

--
Paul Biggar
paul.biggar@gmail.com