From: Richard Henderson <rth@redhat.com>
To: Fergus Henderson <fjh@cs.mu.oz.au>
Cc: Peter Gerwinski <peter@gerwinski.de>, gcc@gcc.gnu.org
Subject: Re: How to use the garbage collector?
Date: Tue, 02 Jan 2001 01:06:00 -0000 [thread overview]
Message-ID: <20010102010647.A27917@redhat.com> (raw)
In-Reply-To: <20010102185745.B2460@hg.cs.mu.oz.au>
On Tue, Jan 02, 2001 at 06:57:45PM +1100, Fergus Henderson wrote:
> 1. Delete obstack code.
> 2. Register your roots.
> 3. Mark your types.
Yep.
> I think you probably also need to register any local variables which
> contain pointers to GC'd memory, and which are not linked to from
> other memory that will be traced, and which are live when ggc_collect
> () is called.
See the use of ggc_push_context and ggc_pop_context in e.g.
cp/semantics.c for an alternative to marking local variables.
r~
next prev parent reply other threads:[~2001-01-02 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 18:51 Peter Gerwinski
2001-01-01 23:58 ` Fergus Henderson
2001-01-02 1:06 ` Richard Henderson [this message]
2001-01-02 10:21 ` Mark Mitchell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010102010647.A27917@redhat.com \
--to=rth@redhat.com \
--cc=fjh@cs.mu.oz.au \
--cc=gcc@gcc.gnu.org \
--cc=peter@gerwinski.de \
/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).