[movitz-cvs] CVS update: public_html/movitz.html

Wed Apr 7 01:13:41 UTC 2004

Update of /project/movitz/cvsroot/public_html
In directory common-lisp.net:/tmp/cvs-serv13569

Modified Files:
	movitz.html 
Log Message:
Slight change to description of GC: interrupt frames are now somewhat
supported.

Date: Tue Apr  6 21:13:41 2004
Author: ffjeld

Index: public_html/movitz.html
diff -u public_html/movitz.html:1.6 public_html/movitz.html:1.7

--- public_html/movitz.html:1.6	Tue Mar 30 03:35:32 2004
+++ public_html/movitz.html	Tue Apr  6 21:13:41 2004
@@ -10,7 +10,7 @@
  Author:        Frode Vatvedt Fjeld <frodef at acm.org>
  Created at:    Wed Nov  5 09:55:54 2003
                 
- $Id: movitz.html,v 1.6 2004/03/30 08:35:32 ffjeld Exp $
+ $Id: movitz.html,v 1.7 2004/04/07 01:13:41 ffjeld Exp $
                 
 -->
 
@@ -20,7 +20,7 @@
 </head>
 <body>
 <h1>Movitz: A Common Lisp OS development platform</h1>
-<tt>$Id: movitz.html,v 1.6 2004/03/30 08:35:32 ffjeld Exp $</tt>
+<tt>$Id: movitz.html,v 1.7 2004/04/07 01:13:41 ffjeld Exp $</tt>
 
 <h2><a href="files/">Files</a></h2>
 <p> The latest <a href="files/los0.img"> los0 kernel image</a> and its
@@ -157,7 +157,7 @@
 
 <li> <tt>map-stack-words</tt> works similarly for a control stack. A
 stack is wrapped as a vector specialized to <tt>(unsigned-byte
-32)</tt> in memory, so it will not recognized as pointers by
+32)</tt> in memory, so it will not be recognized as pointers by
 e.g. <tt>map-heap-words</tt>. Hence, this function must be used
 explicitly over each live control stack in order to capture all
 pointers in the system. Another reason why stacks are special, is that
@@ -179,8 +179,10 @@
 to be promoted from the two 256 KB buffers, so you cannot have more
 than this amount of live, dynamically allocated data. You may trigger
 the GC process explicitly with <tt>(stop-and-copy)</tt>. Note that
-there are still several rough edges remaining this GC implementation,
-e.g. it will not behave across any kind of interrupt.
+there are still rough edges remaining this GC implementation.
+E.g. there is no support for code-vectors migrating yet, although this
+will only become an issue when new code-vectors are consed up (i.e. by
+incremental compilation of some sort).
 
 <h2>About OS design in Common Lisp</h2>
 



