I've managed to implement a generator in Java
using the patch provided by Lukas Stadler:
http://weblogs.java.net/blog/forax/archive/2009/11/19/holy-crap-jvm-has-coroutinecontinuationfiber-etc
Rémi
--
You received this message because you are subscribed to the Google Groups JVM
Languages group.
On Nov 16, 7:33 pm, Jon Harrop j...@ffconsultancy.com wrote:
I see allocation as contention because the heap is a global shared resource.
If you want to recover the performance of the previous generation of
standalone languages with GCs optimized for rapid recycling on a single
thread (e.g.
I suppose different JVMs tackle it different ways, but on the IBM
iSeries JVM we kept a virtual function table for each class and called
through that. Interpreted functions contained a pointer to the
interpreter in the VFT, and a pointer to the method table entry in the
this class was passed as a
On Friday 20 November 2009 02:30:13 Daniel Hicks wrote:
On Nov 16, 7:33 pm, Jon Harrop j...@ffconsultancy.com wrote:
I see allocation as contention because the heap is a global shared
resource. If you want to recover the performance of the previous
generation of standalone languages with
The SLOTS case is a little surprising, in that the call should have
been quickly inlined and reduced to the array addressing case. The
array-addressing case is also a bit surprising -- a good JIT should
have been able to pull the array bounds check out of the loop,
reducing the loop body to the
