Displaying 5 results from an estimated 5 matches for "prtnextactiv".
2011 Jul 07
0
[LLVMdev] Improving Garbage Collection
...ion 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 function. To go to the next activation on the call stack, you then call the runtime's prtNextActivation. There are routines to determine when you've got to the bottom of the call stack as well. In addition, there are routines for performing other (non-GC) operations the stack iterator's activation, such as looking up data associated with the SPAN construct (taken from C--) or exception...
2011 Jul 07
2
[LLVMdev] Improving Garbage Collection
...tion 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 function.
To go to the next activation on the call stack, you then call the runtime's
prtNextActivation. There are routines to determine when you've got to the
bottom of the call stack as well. In addition, there are routines for
performing other (non-GC) operations the stack iterator's activation, such
as looking up data associated with the SPAN construct (taken from C--) or
exception...
2011 Jul 07
4
[LLVMdev] Improving Garbage Collection
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
>
2011 Jul 07
1
[LLVMdev] Improving Garbage Collection
...d. 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 function.
> To go to the next activation on the call stack, you then call the runtime's
> prtNextActivation. There are routines to determine when you've got to the
> bottom of the call stack as well. In addition, there are routines for
> performing other (non-GC) operations the stack iterator's activation, such
> as looking up data associated with the SPAN construct (taken from C-...
2011 Jul 07
0
[LLVMdev] Improving Garbage Collection
...ion 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 function. To go to the next activation on the call stack, you then call the runtime's prtNextActivation. There are routines to determine when you've got to the bottom of the call stack as well. In addition, there are routines for performing other (non-GC) operations the stack iterator's activation, such as looking up data associated with the SPAN construct (taken from C--) or exception...