sb-bsd-sockets: foreign memory leak in GET-PROTOCOL-BY-NAME

[sbcl.git] / NEWS

diff --git a/NEWS b/NEWS
index ff33e74..d0c7328 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,11 +1,28 @@
 ;;;; -*- coding: utf-8; fill-column: 78 -*-
 changes relative to sbcl-1.0.53:
+  * minor incompatible changes:
+    ** RENAME-FILE on a symbolic links used to rename the linked-to file instead
+       of the link.
+    ** DELETE-DIRECTORY on symbolic link to a directory used to delete the
+       directory, but now signal an error instead. Use TRUENAME to resolve
+       the pathname if you wish to delete the linked directory, and DELETE-FILE
+       if you wish to delete the
+  * enchancement: on CHENEYGC targets, SB-KERNEL:MAKE-LISP-OBJ now does
+    the same validation of pointer objects as GENCGC does, instead of a
+    comparatively weak bounds-check against the heap spaces.
+  * enhancement: on win32, ABS of complex floats guards better against
+    overflows. (lp#888410)
   * bug fix: on 64-bit targets, atomic-incf/aref does index computation
     correctly, even on wide-fixnum builds. (lp#887220)
   * bug fix: (directory "foo/*/*.*") did not follow symlinks in foo/ that
     resolved to directories.
   * bug fix: SB-KERNEL:MAKE-LISP-OBJ on GENCGC no longer categorically
     refuses to create SIMPLE-FUN objects.
+  * bug fix: type mismatch when assigning to lexical variables no longer
+    result in fasl-dumping internal type objects. (lp#890750)
+  * bug fix: type mismatch on (setf aref) and function return values no
+    longer result in fasl-dumping internal type objects.
+  * bug fix: SB-BSD-SOCKETS:GET-PROTOCOL-BY-NAME leaked foreign memory.
 
 changes in sbcl-1.0.53 relative to sbcl-1.0.52:
   * enhancement: on 64-bit targets, in src/compiler/generic/early-vm.lisp,