common-lisp/sbcl.sbcl
1
0
Fork 0
mirror of git://git.code.sf.net/p/sbcl/sbcl synced 2026-09-10 07:26:40 -04:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

0.6.11:

Browse source 
tag sbcl_0_6_11
This commit is contained in:
William Harold Newman 2001-02-25 18:20:45 +00:00
parent 13bb6d7a14
commit 3fe8a354e4
2 changed files with 4 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
TODO
View file

@ -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

2
version.lisp-expr
View file

@ -15,4 +15,4 @@
;;; versions, and a string like "0.6.5.12" is used for versions which
;;; aren't released but correspond only to CVS tags or snapshots.
"0.6.10.23"
"0.6.11"