mirror of
git://git.sv.gnu.org/emacs.git
synced 2026-01-20 19:42:53 -08:00
Using "cold end" rather than "bottom" of the stack, to avoid ambiguity.
Copied from Perforce Change: 189106 ServerID: perforce.ravenbrook.com
This commit is contained in:
parent
989d78b1f4
commit
ecff19832b
1 changed files with 7 additions and 6 deletions
|
|
@ -148,12 +148,13 @@ Every thread's :term:`registers` and :term:`control stack` potentially
|
|||
contain references to allocated objects, so should be registered as a
|
||||
root by calling :c:func:`mps_root_create_stack`.
|
||||
|
||||
The MPS's stack scanner needs to know how to find the bottom of the
|
||||
part of the stack to scan. The bottom of the relevant part of stack
|
||||
can be found by taking the address of a local variable in the function
|
||||
that calls the main work function of your thread. You should take care
|
||||
to ensure that the work function is not inlined so that the address is
|
||||
definitely in the stack frame below any potential roots.
|
||||
The MPS's stack scanner needs to know how to find the :term:`cold end`
|
||||
of the part of the stack to scan. The :term:`cold end` of the relevant
|
||||
part of stack can be found by taking the address of a local variable
|
||||
in the function that calls the main work function of your thread. You
|
||||
should take care to ensure that the work function is not inlined so
|
||||
that the address is definitely in the stack frame below any potential
|
||||
roots.
|
||||
|
||||
.. index::
|
||||
single: Scheme; thread root
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue