megamorphic lambda prevention

[Jochen Theodorou]

Am 21.06.2012 13:57, schrieb Krystal Mok:
> That's "the inlining problem" that Cliff Click was talking about [1], right?

yes, the issue was actually mentioned more than once on this list already

> I wonder how well the new interpreter design in Graal would handle this
> kind of case, since it's supposed to have picked the good parts from
> trace-based compilation, but without actually having to do tracing.
> Can't wait to see more details of it at this year's JVM Language Summit.

If I understood Thomas right, then Graal doesn't have that problem. 
Afaik hotspot doesn't have to have that problem too. It just was a 
design decision not to make call site caching per execution path. Afaik 
chaning that now would take quite some effort, but is not impossible.

bye blackdrag

-- 
Jochen "blackdrag" Theodorou - Groovy Project Tech Lead
blog: http://blackdragsview.blogspot.com/
german groovy discussion newsgroup: de.comp.lang.misc
For Groovy programming sources visit http://groovy-lang.org