search for: prtenumeraterootsofactiv

...by the current frame or a subsequent frame. The stack iterator also contains a virtual frame number that basically allows an unwinder to see logical activations instead of physical activations that may combine multiple logical activations via inlining. You can then call another runtime function, prtEnumerateRootsOfActivation, to ask for the roots associated with the given stack iterator's current activation to be enumerated. To this function, you pass a PrtRseInfo struct that contains a callback that gets invoked once per live ref found and a opaque environment variable passed (unexamined) onto the callback f...

...t if only one half was in a register and the other half on the stack?) I'm guessing that the right answer is "don't do that" - meaning, don't allow this data structure to be sliced in that way, at least not during a safe point. ** You can then call another runtime function, prtEnumerateRootsOfActivation, to ask for the roots associated with the given stack iterator's current activation to be enumerated. To this function, you pass a PrtRseInfo struct that contains a callback that gets invoked once per live ref found and a opaque environment variable passed (unexamined) onto the callback f...

On 07.07.2011 08:31, Nate Fries wrote: > On 7/6/2011 6:24 PM, Talin wrote: >> The LLVM code generators and analysis passes have a much more >> thorough knowledge of SSA value lifetimes than frontends do, and >> therefore could avoid spilling and reloading of values when it wasn't >> needed. > Although this would indeed be nice, it is not done by similar >

...core seems > important so you can handle ref params and refs in registers. You can > define it as data structures in the core and implement a library on top.** > *** > > ** > I'm in agreement here. > ** > > **** > > You can then call another runtime function, prtEnumerateRootsOfActivation, > to ask for the roots associated with the given stack iterator's current > activation to be enumerated. To this function, you pass a PrtRseInfo struct > that contains a callback that gets invoked once per live ref found and a > opaque environment variable passed (unexamined)...

...igher level that LLVM should not have to worry about but having such a generalized ref type in the core seems important so you can handle ref params and refs in registers. You can define it as data structures in the core and implement a library on top. You can then call another runtime function, prtEnumerateRootsOfActivation, to ask for the roots associated with the given stack iterator's current activation to be enumerated. To this function, you pass a PrtRseInfo struct that contains a callback that gets invoked once per live ref found and a opaque environment variable passed (unexamined) onto the callback f...