From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: jantien@xs4all.nl, guile-devel@gnu.org
Subject: Re: stumped by scm_car/scm_cdr
Date: Sun, 24 Oct 2004 14:25:56 +0200 [thread overview]
Message-ID: <16763.40788.741482.351651@byrd.xs4all.nl> (raw)
In-Reply-To: <lju0sryl3n.fsf@troy.dt.e-technik.uni-dortmund.de>
marius.vollmer@uni-dortmund.de writes:
> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
> > I've added a check to scm_cell/scm_double_cell that calls abort() if
> > GC is running.
>
> Well, OK. Another idea is to set the freelists to NULL during GC
> explicitely, thus causing scm_cell etc to call scm_gc_for_newcell
> immediately, and scm_gc_for_newcell could then check whether the GC is
> already running. That would not make scm_cell etc slower for the
> usual case that the GC is in fact not running. Could you try that
> variant?
I tried to look at this, but scm_i_freelist is now a thread-specific
variable. I'm unsure if and how they should all be set to null or
SCM_EOL.
--
Han-Wen Nienhuys | hanwen@xs4all.nl | http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-10-24 12:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 23:29 stumped by scm_car/scm_cdr Han-Wen Nienhuys
2004-09-25 15:54 ` Marius Vollmer
2004-09-25 23:19 ` Han-Wen Nienhuys
2004-09-29 15:37 ` Marius Vollmer
2004-10-06 23:44 ` Han-Wen Nienhuys
2004-10-07 18:52 ` Han-Wen Nienhuys
2004-10-07 21:55 ` Marius Vollmer
2004-10-07 22:12 ` Marius Vollmer
2004-10-07 22:51 ` Han-Wen Nienhuys
2004-10-07 23:41 ` Han-Wen Nienhuys
2004-10-18 17:47 ` Marius Vollmer
2004-10-24 12:25 ` Han-Wen Nienhuys [this message]
2004-11-04 16:49 ` Marius Vollmer
2004-11-08 6:48 ` Dirk Herrmann
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=16763.40788.741482.351651@byrd.xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=guile-devel@gnu.org \
--cc=jantien@xs4all.nl \
/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).