From: Andy Wingo <wingo@pobox.com>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: Mark H Weaver <mhw@netris.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: redoing SCM representation in 2.2
Date: Sun, 15 May 2011 17:35:04 +0200 [thread overview]
Message-ID: <m3vcxcasev.fsf@unquote.localdomain> (raw)
In-Reply-To: <BE0DE415-88B7-422C-BE8A-4F5315F8044D@raeburn.org> (Ken Raeburn's message of "Sun, 15 May 2011 05:02:17 -0400")
On Sun 15 May 2011 11:02, Ken Raeburn <raeburn@raeburn.org> writes:
> Is that really any more of an issue this way than with the current
> encoding -- if not for SCM, then for heap data structures including both
> SCM objects and integers or characters? I thought the GC code already
> had to cope with things looking like they could be pointers but not
> actually corresponding to anything allocated via the GC library.
It's not an issue for SCM values. The Scheme stack has only Scheme
values, so there's no problem there either; and the C stack is small,
mostly ephemeral, and there is good blacklisting, so no problem there
either, AFAIK. Heap values which contain no GC-controlled pointers are
allocated "atomically", which means the GC doesn't trace them. So the
issue would only be with structures which are traced by GC and include
both, and there are very few of those.
Regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-05-15 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 10:17 redoing SCM representation in 2.2 Andy Wingo
2011-05-12 11:12 ` nalaginrut
2011-05-12 12:50 ` Stefan Israelsson Tampe
2011-05-13 22:08 ` Mark H Weaver
2011-05-14 9:47 ` Andy Wingo
2011-05-15 9:02 ` Ken Raeburn
2011-05-15 15:35 ` Andy Wingo [this message]
2011-05-15 9:00 ` Ken Raeburn
2011-05-15 15:47 ` Andy Wingo
2011-05-15 20:43 ` Ken Raeburn
2011-05-16 9:40 ` Andy Wingo
2011-05-17 18:59 ` Mark H Weaver
2011-05-19 7:58 ` Ken Raeburn
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=m3vcxcasev.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=raeburn@raeburn.org \
/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).