harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Chow" <simon.harm...@gmail.com>
Subject Re: [drlvm][jit] Instoptimizer in MemoryValueNumberingPass
Date Mon, 19 May 2008 05:24:04 GMT
Thanks for your suggestion.
IMO, the current information in Inst of TauLdInd is not enough for read
barriers generation.
That's the reason why I tend to implement a new opcode TauLdRef.
For example, there is no ref holding object reference (like 'base' in
TauStRef) in TauLdInd, but it is necessary for read barrier.
Additionally, IMO, not all the 'TauLd' need to be intercepted, my TauLdRef
only represents the ref loading that requires barrier.
Do you think it is reasonable?


2008/5/19 George Timoshenko <george.timoshenko@gmail.com>:

> Hi.
> You are trying to work and solve problems in HLO.
> What do you thing on the current write barrier implementation?
> WBs appeare only in code selector. HLO knows nothing about them.
> Why don't use similar approach and just implement read barriers generation
> in CodeSelector?
> Doing this you should not care on MemOpt and other HLO stuff.
> George.

>From : Simon.Chow@Software School of Fudan University

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message