unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Lynn Winebarger <owinebar@free-expression.org>
Subject: Re: new GC code merged
Date: Sat, 17 Aug 2002 00:30:35 -0500	[thread overview]
Message-ID: <02081700303500.19624@locke.free-expression.org> (raw)
In-Reply-To: <15692.29931.82055.847632@blauw.xs4all.nl>

On Saturday 03 August 2002 19:27, Han-Wen wrote:
> I merged my new GC code into HEAD. It's tagged before-hanwen-gc-change
> and after-hanwen-gc-change. Here the preliminary notes for it. I'm not
> sure what else you want me to document, but I think the current change
> log entries are not verbose enough. Anyway, here goes:
> 
       Excuse my ignorance.  The notes in tag.h indicate that the least significant
bit of the 2nd word of a cell is used for marking.  I was reading gc.h and it
appears the mark bits are stored separately.  On the other hand, I looked
at a copy of guile from before your changes and it might also have used separate
mark bitvectors.  
     So is that lsb of the second word of a cell actually free for some other use besides
marking?

Lynn


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2002-08-17  5:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-04  0:27 new GC code merged Han-Wen
2002-08-05 18:18 ` Marius Vollmer
2002-08-17  5:30 ` Lynn Winebarger [this message]
2002-08-18  0:36   ` Han-Wen Nienhuys
2002-08-18  1:31     ` Lynn Winebarger

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=02081700303500.19624@locke.free-expression.org \
    --to=owinebar@free-expression.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).