Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43885
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.46.29 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=DmW2nZDPBXoCKvV9a89s6e90ZHq0hN++AsEXGdjbj3ZYa1skWkggg/lutw6+dbNKCM
         lr0pZJPFgBUsUPWW5EZHoLVivd3HKVx2UXgh9OZWZQtFoNGDF6ZHloCXI0mYtGKj77Ox
         B32gNOE0EEpB/cbjBlTtRqCXhm0kqFrXpBvr0=
MIME-Version: 1.0
In-Reply-To: <497872B8.60807@zend.com>
References: <A4BF27E9DF4D4E64AB2164332B12410D@carla>
	 <155749706.20090117211737@marcus-boerger.de> <497872B8.60807@zend.com>
Date: Mon, 11 May 2009 15:47:41 -0300
Message-ID: <bcb7aa500905111147m5c4c63ach362ca45f7d89afe0@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: Marcus Boerger <helly@php.net>, Timm Friebe <thekid@thekid.de>, internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Method call improvements
From: guilhermeblanco@gmail.com (Guilherme Blanco)

Hi guys,

What's the status on this one?!

It's an important optimization that should be considered. Save more
than a million method calls on a framework does not worth?
None gave a final word on this subject.

I could not see this commited in 5.3 neither in HEAD.
So...can someone notify me about the status of this???


Cheers,

On Thu, Jan 22, 2009 at 10:20 AM, Dmitry Stogov <dmitry@zend.com> wrote:
>
> Marcus Boerger wrote:
>
>> Aren't we able to bind these at least partially to the function call
>> opcode, in case we know they are constant? If all is constsnt we could
>> even store the whole lookup in the opcode. Well you'd have to convince
>> Zend to do that because os far they have always been against this
>> approach.
>
> We can't modify opcode it self as it'll break opcode caches.
>
> However we can introduce some indirect table associated with op_array, wh=
ich
> can be used to implement inline caches without direct opcode modification
> (in the same way as IS_CV variables work). There are a lot of papers abou=
t
> polymorphic inline caches (e.g.
> http://research.sun.com/self/papers/pics.html) which we probably should u=
se
> to not to invite bicycle.
>
> Thanks. Dmitry.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



--=20
Guilherme Blanco - Web Developer
CBC - Certified Bindows Consultant
Cell Phone: +55 (16) 9215-8480
MSN: guilhermeblanco@hotmail.com
URL: http://blog.bisna.com
S=C3=A3o Paulo - SP/Brazil