changes in sbcl-0.7.7 relative to sbcl-0.7.6:
* An alpha-quality port to the parisc architecture running Linux,
- based on the old CMUCL backend has been made. This, even more so
+ based on the old CMUCL backend, has been made. This, even more so
than the other backends, should be considered still a work in
progress; known problems include that the Linux kernel in 64-bit
mode does not propagate the correct sigcontext structure to
SB-KERNEL:CONTROL-STACK-EXHAUSTED condition (subclass of
STORAGE-CONDITION) is signalled, so stack exhaustion can no longer
be caught using IGNORE-ERRORS.
+ * Bugs 65, 70, and 109 fixed: The compiler now preserves invariants
+ correctly when transforming recursive LABELS functions to LETs.
+ (thanks to Alexey Dejneka)
* Bug 48a./b. fixed: SYMBOL-MACROLET now refuses to bind symbols
that are names of constants or global variables.
* Bug fix: DEFINE-ALIEN-ROUTINE now declaims the correct FTYPE for
* The fasl file version number has changed again. (because of the
bug fix involving the names of PCL MAKE-INSTANCE functions)
+changes in sbcl-0.7.8 relative to sbcl-0.7.7:
+ * A beta-quality port to the mips architecture running Linux,
+ based on the old CMUCL backend, has been made. It has been tested
+ on a big-endian kernel, and works sufficiently well to be able to
+ rebuild itself; it has not been tested in little-endian mode.
+ * fixed bug 120a: The compiler now deals correctly with IFs where
+ the consequent is the same as the alternative, instead of
+ misderiving the return type. (thanks to Alexey Dejneka)
+ * fixed bug 113: Logical pathnames are now dumpable (the logical
+ host is resolved at load-time, throwing an error if it is not
+ found).
+ * fixed bug 174: FORMAT's error message is slightly clearer when a
+ non-printing character is used in a format directive.
+ * fixed several bugs in compiler checking of type declarations, i.e.
+ violations of the Python "declarations are assertions" principle
+ (thanks to Alexey Dejneka)
+ * fixed several bugs in PCL's error checking (thanks to Gerd
+ Moellmann)
+
planned incompatible changes in 0.7.x:
* When the profiling interface settles down, maybe in 0.7.x, maybe
later, it might impact TRACE. They both encapsulate functions, and