X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=TODO;h=bb153be25ddebc5fc6084818df42a1832b86378a;hb=21223eedf790450dc484907c2bedf2b9bdaa80bf;hp=f0e4e393ff3e0848821f13c424659d554e473643;hpb=943f38e6232a69ab1bbcfb2c86801eea391f8ae1;p=sbcl.git

diff --git a/TODO b/TODO
index f0e4e39..bb153be 100644
--- a/TODO
+++ b/TODO
@@ -70,6 +70,9 @@ FIX:
 	?? Replace it with a system where fasl output files live in the 
 	  same directories as the sources and have names a la
 	  "foo.fasl-from-host and "foo.fasl-from-xc".
+	?? (Perhaps something else will be required in order to port
+	to Microsoft Windows, since its filesystem doesn't have
+	symbolic links.)
 -------------------------------------------------------------------------------
 PROBLEM:
 	    It might be good to use the syntax (DEBUGGER-SPECIAL *PRINT-LEVEL*)
@@ -121,21 +124,6 @@ types, or whatever, and also have no other uses as e.g. flags) and
 delete them. This should make the system core a little smaller, but
 is mostly useful just to make the source code smaller and simpler.
 
-The eventual plan is for SBCL to bootstrap itself in two phases. In
-the first phase, the cross-compilation host is any old ANSI Common
-Lisp (not necessarily SBCL) and the cross-compiler won't handle some
-optimizations because the code it uses to implement them is not
-portable. In the second phase, the cross-compilation host will be
-required to be a compatible version of SBCL, and the cross-compiler
-will take advantage of that to implement all optimizations. The
-current version of SBCL only knows how to do the first of those two
-phases, with a fully-portable cross-compiler, so some optimizations
-are not done. Probably the most important consequence of this is that
-because the fully-portable cross-compiler isn't very smart about
-dealing with immediate values which are of specialized array type
-(e.g. (SIMPLE-ARRAY (UNSIGNED-BYTE 4) 1)) the system sometimes has to
-use unnecessarily-general array types internally.
-
 adding new FOPs to provide something like CMU CL's FOP-SYMBOL-SAVE and
 FOP-SMALL-SYMBOL-SAVE functionality, so that fasl files will be more
 compact. (FOP-SYMBOL-SAVE used *PACKAGE*, which was concise but allowed