[Sbcl-announce] sbcl-2.5.5 released

[Christophe R. <cs...@ca...>]

Dear all,

The SBCL 2.5.5 release is now tagged, with artifacts beginning to make
their way to SourceForge.  The freeze interval took rather longer than
usual because of the late discovery of an issue relating to automatic
stack allocation in slightly more cases than necessary: the culprint
changes have been reverted, but we hope for a less incorrect
implementation of the same idea in the next release cycle.  The changes
that have survived this release cycle are listed below.

Best wishes,

Christophe

changes in sbcl-2.5.5 relative to sbcl-2.5.4:
  * minor incompatible change: the output from TRACE is now prefixed by a
    FRESH-LINE on *TRACE-OUTPUT*.
  * platform support:
    ** On Linux, the system is better at negotiating with the kernel to find
       locations for Lisp memory spaces, succeeding more often than
       previously.
  * bug fix: resolve signed/unsigned char mismatch in RUN-PROGRAM on Windows.
    (lp#2110525, reported by awlygj)
  * bug fix: compiler confusion given sufficiently complex derived type
    constraints.  (lp#2109902)
  * bug fix: compiler inconsistency in low-level representation leading to
    inconsistent transformations.  (lp#2109837)
  * bug fix: return NIL from calls to DOCUMENTATION on illegal function names.
  * bug fix: calls to APPLY or VALUES-LIST on some combinations of constant
    arguments could lose the constant nature after transformation.  (thanks to
    Hayley Patton)
  * optimization: some micro-improvements to bignum operations, particularly
    on x86-64 and arm64
  * optimization: allow the result of MAKE-STRING to be allocated on the stack
    when :element-type is unknown.
  * optimization: the compiler will recognize the use of ZEROP on the results
    of LENGTH and REM (on suitable operands) to avoid full computation of the
    intermediate result.