+* incompatible change: The default fasl file extension has changed
+ to ".fasl", for all architectures. (No longer ".x86f" and ".axpf".)
+* The EVAL-WHEN code has been rewritten to be ANSI-compliant, and
+ various related bugs (IR1-1, IR1-2, IR1-3, IR1-3a) have gone away.
+ Since the code is newer, there might still be some new bugs
+ (though not as many as before Martin Atzmueller's fixes:-). But
+ hopefully any remaining bugs will be simpler, less fundamental,
+ and more fixable then the bugs in the old IR1 interpreter code.
+* The IR1 interpreter, byte compiler, and byte interpreter are gone.
+ It's long been my plan to remove the IR1 interpreter while making
+ EVAL-WHEN ANSI-compliant. It turned out that a cascade of changes
+ caused by EVAL-WHEN ANSIness would have required fairly simple
+ changes to the byte compiler; except they turned out to be quite
+ difficult. This, plus the new familiarity with the byte compiler
+ in general that I picked up as I worked on this specific problem,
+ reduced my opinion of its maintainability enough that I deleted it
+ instead of trying to fix it.
+* The compiler, especially the IR1 phase of the compiler, has been
+ tweaked somewhat to support the new implementation of DEFUN and
+ of the static linking hack used for cold init. In particular,
+ the property of "is externally visible" is now orthogonal to
+ the property of "is optimized/specialized for being called
+ at LOAD time, with no arguments and no argument checking".
+ The old FUNCTIONAL-KIND=:TOP-LEVEL type code which
+ conflated these two properties has been replaced with the
+ FUNCTIONAL-HAS-EXTERNAL-REFERENCES-P flag. This has minor
+ beneficial consequences for the logic of #'CL:COMPILE and other
+ things. Like the rewrite of EVAL, it has also quite possibly
+ introduced some new bugs, but since the new logic is simpler and
+ more orthogonal, hopefully it will be easier to clean up bugs
+ in the new code than it was in the old code.
+* The rewritten compiler is still a little unsteady on its feet.
+ In particular, the debugging information it produces is sometimes
+ broken, and the support for inlining FOO when you
+ (DECLAIM (INLINE FOO)) then do (DEFUN FOO ..) in a non-null
+ lexical environment has been temporarily weakened (because the
+ old clever code depended on correct debugging information).