From: "ZHUO Qingliang (KDr2)" via General Guile related discussions <guile-user@gnu.org>
To: Guile User <guile-user@gnu.org>
Subject: How does GC know what SCM objects are on the stack?
Date: Wed, 29 Jan 2020 06:34:15 +0000 (UTC) [thread overview]
Message-ID: <660410322.617602.1580279655137@mail.yahoo.com> (raw)
In-Reply-To: 660410322.617602.1580279655137.ref@mail.yahoo.com
I just read the docs about GC, if I understand it correctly, in a c program, all static variables, global variable, and local variables that hold SCM objects are registered to GC protection automatically.
I want to know how does the GC make this, could anyone give me a clue?
Many thanks.
next parent reply other threads:[~2020-01-29 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <660410322.617602.1580279655137.ref@mail.yahoo.com>
2020-01-29 6:34 ` ZHUO Qingliang (KDr2) via General Guile related discussions [this message]
2020-01-29 7:55 ` How does GC know what SCM objects are on the stack? ZHUO Qingliang (KDr2) via General Guile related discussions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=660410322.617602.1580279655137@mail.yahoo.com \
--to=guile-user@gnu.org \
--cc=zhuoql@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).