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
Ming,
The above is just a consideration for infrastructure. I have already
implemented the write barrier code in jet for some GC developed in C.
It has already been tested and attached file is the patch.
Cool ! Thanks for the patch !
I'm not too familiar with GC stuff, but seems you are
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 barrier is actually Java code. Injecting a
vm helper
hi, guys
The way to use gen_invoke to call a Java write barrier should work, and
the better way may be inlining the barrier code. Maybe jet can not do
inlining, but jitrino.opt should do it.
Alex's idea is not so bad. It is right that the cost will be high if
we'll have a JNI call on every
All,
I have been reading both MMTK and Jitrino.JET sources with write
barrier design specifically in mind. Below are my current thoughts.
Integrating MMTK with Jitrino.JET. In Compiler::gen_field_op(), use
gen_invoke() to emit a call to
org.mmtk.plan.PlanLocal.writeBarrier(ObjectReference src,
