Weldon Washburn wrote:
Alex,
Sorry for taking so long to answer your questions below. Please see
the response inline.
Weldon
On 6/27/06, Alex Astapchuk [EMAIL PROTECTED] wrote:
AFAIR from the recent thread, to implement WB for MMTk support, I have
to emit calls of
On 6/30/06, Alex Astapchuk [EMAIL PROTECTED] wrote:
Actually, the simplest form of write barrier would be one, single
parameter -- a ref ptr to the object getting scribbled on. I suspect
Hmmm...
Seems I have a misunderstanding here - how comes a single ref ?
What I was thinking of, is
Alex,
Sorry for taking so long to answer your questions below. Please see
the response inline.
Weldon
On 6/27/06, Alex Astapchuk [EMAIL PROTECTED] wrote:
AFAIR from the recent thread, to implement WB for MMTk support, I have
to emit calls of
org.mmtk.plan.PlanLocal.writeBarrier(
Weldon,
I can guess what 'src' is - this is the object being written, right ?
But could you please point me what all other args are ?
Can't we go without all the stuff and have only 2 args - an
object being written and the destination class/array/instance ? :-)
Actually, the simplest form
Hi Alex,
Comment inline below.
On 6/27/06, Alex Astapchuk [EMAIL PROTECTED] wrote:
Weldon,
Weldon Washburn wrote:
It would be really nice if jitrino.jet allowed the write barrier to be
selected at the start of jitting an individual method. Is this
possible?
Sure. Currently, jitrino.jet
Weldon,
Weldon Washburn wrote:
It would be really nice if jitrino.jet allowed the write barrier to be
selected at the start of jitting an individual method. Is this
possible?
Sure. Currently, jitrino.jet handles some of OpenMethodExecutionParams
flags to instrument the jitted code.
The
It would be really nice if jitrino.jet allowed the write barrier to be
selected at the start of jitting an individual method. Is this
possible?
The selections would be mutually exclusive:
1)
no write barrier (for the existing GCV4)
2)
write barrier written in Java (for MMTk)
3)
write barrier
