Re: Method call improvements

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, which > 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 about > polymorphic inline caches (e.g. > http://research.sun.com/self/papers/pics.html) which we > probably should use > to not to invite bicycle. > > Thanks. Dmitry. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Guilherme Blanco - Web Developer CBC - Certified Bindows Consultant Cell Phone: +55 (16) 9215-8480 MSN: guilhermeblanco@hotmail.com URL: http://blog.bisna.com São Paulo - SP/Brazil