George 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?
Thanks 2008/5/19 George Timoshenko <[EMAIL PROTECTED]>: > 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 : [EMAIL PROTECTED] School of Fudan University
