harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao-Feng Li" <xiaofeng...@gmail.com>
Subject Re: [DRLVM] (JIRA 1580) write barrier implementation for JET
Date Thu, 28 Sep 2006 00:59:21 GMT
Thanks to Egor and Gregory's responses to the JET write barrier patch.
Those help. I was away from JIT development for a while. :-)

Since the patch is small, if needed, please feel free to modify it as
a JIRA update, or a committer to merge it then we submit new patch
later. Basically the write barrier should be as small (quick) as
possible and involves no additional VM runtime operations. A view to
write barrier can be that, it is only an extended bytecode of the
orignal reference store one. That means, we can implement it in anyway
appropriate as long as the semantics of the reference store is kept,
either in JIT IR, in LIL, in asm or as a function call. Performance
and flexibility are the main goals. The performance is easy to
understand, the flexibility refers to that a GC developer probably can
conveniently change the write barrier implementation.

As I know, a volunteer (Mikhail Fursov?) is writing helper inlining
for DRLVM. Hopefully that will be the ultimate solution for write
barrier implementation. Before that is ready, an intermediate solution
would be acceptable.


> On 27 Sep 2006 17:20:36 +0700, Egor Pasko <egor.pasko@gmail.com> wrote:
> I am curious about the switch
> VM_Global_State::loader_env->use_lil_stubs. Does everything work in
> both true and false? What do we need this switch for? Doesn't it
> induce unnecessary complication/duplication?

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org

View raw message