At 08:31 PM 8/10/00 +0000, Nick Ing-Simmons wrote:
>You just re-invented "look up the name in a hash table" ;-)
>
>You now have one big hash table rather than several small ones.
>Which _may_ give side benefits - but I doubt it.
If we prefigure a bunch of things (hash values of method names, store
package stash pointers in objects, and pre-lookup CVs for objects that are
typed) it'll save us maybe one level of pointer indirection and a type
comparison. If the object isn't the same type we pay for a type comparison
and hashtable lookup.
Not free, but not expensive either. 'Specially if we get way too clever and
cache the new CV and type in the opcode for the next time around, presuming
we'll have the same type the next time through.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
- Re: Method call optimization. Chaim Frenkel
- Re: Method call optimization. Damien Neil
- Re: Method call optimization. Dan Sugalski
- Re: Method call optimization. Nick Ing-Simmons
- Re: Method call optimization. Dan Sugalski
- Re: Method call optimization. Uri Guttman
- Re: Method call optimization. Chaim Frenkel
- Re: Method call optimization. Chaim Frenkel
- Re: Method call optimization. Nick Ing-Simmons
- Re: Method call optimization. Nick Ing-Simmons
- Re: Method call optimization. Dan Sugalski
- Re: Method call optimization. Graham Barr
- Re: Method call optimization. Dan Sugalski
- Re: Method call optimization. Chaim Frenkel
- Re: Method call optimization. Graham Barr
- Re: Method call optimization. Dan Sugalski
- Re: Method call optimization. Graham Barr
- Re: Method call optimization. Dan Sugalski
- Re: Method call optimization. Graham Barr
- Re: Method call optimization. Dan Sugalski
- Re: Method call optimization. Chaim Frenkel
