hi, Stefano
Is the technique you mentioned similar with the Microsoft's NGen?
thanks
-ming
There is one interesting trick that I learned at an IBM presentation
that was done at MIT last year (apologies, I don't remember the name of
the speaker) about the trick of "persisting" the runtime
Weldon,
2006/6/21, Weldon Washburn <[EMAIL PROTECTED]>:
I looked at JIRA 622. It looks like there are 22 pages of new
assembly code and about 26 pages of new java code. Perhaps you could
give us a summary of what the assembly code does and why it can't be
done in Java.
Don't worry about t
We have developed a Java GC with mark-sweep algorithm and integrated it into
the current drlvm code. The key feature is, the GC is not prebuilt into
binary, but loaded and jitted by the VM at runtime. Hopefully it is useful
to the existing efforts porting MMTk to DRLVM. It is actually the rewrite
2006/6/14, Weldon Washburn <[EMAIL PROTECTED]>:
Alex,
It looks like the JIT needs to support write barriers written in both
C as well as Java. Its probably best to think of the C write barrier
as a conventional vm helper call. For a garbage collector written in
Java like MMTk, the write barri
