is no longer a static symbol.)
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
+ 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
+ userspace, and consequently SBCL on a parisc64 kernel will not
+ work yet.
* fixed bug 189: The compiler now respects NOTINLINE declarations for
functions declared in FLET and LABELS. (I.e. "LET conversion" is
suppressed.) Also now that the compiler is looking at declarations
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
* Bug 192 fixed: The internal primitive DATA-VECTOR-REF can now be
constant-folded without failing an assertion. (thanks to Einar
Floystad Dorum for reporting this)
+ * Bugs 123 and 165 fixed: array specializations on as-yet-undefined
+ types are now dealt with more correctly by the compiler.
* Minor incompatible change: COMPILE-FILE-PATHNAME now merges its
OUTPUT-FILE argument with its INPUT-FILE argument, resulting in
behaviour analogous to RENAME-FILE. This puts its behaviour more
* 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:
+ * 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)
+
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