From: Joern Rennecke <amylaar@cygnus.co.uk>
To: rth@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: an experiment with garbage collection
Date: Sat, 09 May 1998 15:57:00 -0000 [thread overview]
Message-ID: <199805092149.WAA26982@phal.cygnus.co.uk> (raw)
In-Reply-To: <19980509012500.06283@dot.cygnus.com>
> (1) We will only garbage collect rtl and trees. Everything else
> will eventually be converted to use plain malloc/free.
I don't think that makes sense. In some cases, there are actaully a lot
of small temporary allocations of non-tree non-rtl objects which
are to be released together; these are most easily handled whith obstacks.
Just cut the obstack usage down to such applications where they are
a natural fit.
next prev parent reply other threads:[~1998-05-09 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-09 3:34 Richard Henderson
1998-05-09 15:57 ` Joern Rennecke [this message]
1998-05-09 21:03 ` Richard Henderson
1998-05-09 22:13 ` Jeffrey A Law
1998-05-09 15:57 ` Francois-Rene Rideau
1998-05-09 11:03 ` Richard Henderson
1998-05-09 16:35 ` John Carr
1998-05-09 16:35 ` Richard Henderson
1998-05-09 21:03 ` David S. Miller
1998-05-10 18:07 Michael Meissner
1998-05-11 15:07 Mike Stump
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=199805092149.WAA26982@phal.cygnus.co.uk \
--to=amylaar@cygnus.co.uk \
--cc=egcs@cygnus.com \
--cc=rth@cygnus.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).