fix doubled unboxed constants when there is no immediate representation

[sbcl.git] / NEWS

diff --git a/NEWS b/NEWS
index 5c384d4..ac2965b 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -7,6 +7,10 @@ changes relative to sbcl-1.0.54:
     ** --arch option can be used to specify the architecture to build for.
        (Mainly useful for building 32-bit SBCL's on x86-64 hosts, not
        full-blows cross-compilation.)
+  * enhancement: extended package prefix syntax <pkgname>::<form-in-package>
+    which allows specifying the name of the package for a whole form.
+  * enhancement: when *READ-EVAL* is true, arrays with element type other than
+    T can be printed readably using #.-based syntax. (Thanks to Robert Brown)
   * enhancement: MAKE-ALIEN signals a storage-condition instead of returning a
     null alien when malloc() fails. (lp#891268)
   * enhancement: SB-EXT:PRINT-UNREADABLY restart for PRINT-NOT-READABLE
@@ -17,8 +21,16 @@ changes relative to sbcl-1.0.54:
     (Thanks to Attila Lendvai)
   * enhancement: BACKTRACE and DESCRIBE now bind *PRINT-CIRCLE* to T, and
     generally behave better when errors occur during printing.
+  * enhancement: the test runner now takes a --report-skipped-tests argument
+    to report the individual tests skipped as well as the number of skipped
+    tests.
+  * enhancement: undefined functions now appear in backtraces as ("undefined
+    function") instead of ("bogus stack frame") on x86oids.
   * optimization: the compiler is smarter about representation selection for
     floating point constants used in full calls.
+  * optimization: the compiler no longer refuses to coerce large fixnums to
+    single floats inline, except on x86 where this limitation is still
+    necessary.
   * bug fix: deadlock detection could report the same deadlock twice, for
     two different threads. Now a single deadlock is reported exactly once.
   * bug fix: interval-arithmetic division during type derivation did not
@@ -41,6 +53,11 @@ changes relative to sbcl-1.0.54:
   * bug fix: non-toplevel DEFSTRUCT signaled a style warning for unknown type.
   * bug fix: redefining a function whose previous definition contained an
     unknown type no longer causes a style-warning. (lp#806243)
+  * bug fix: undefined functions now appear in backtraces as ("undefined
+    function") instead of ("bogus stack frame") on non-x86oids.
+  * bug fix: backtraces are no longer cut off at ("undefined function") when
+    called under certain circumstances (involving a caller-allocated stack
+    frame) on PPC.
 
 changes in sbcl-1.0.54 relative to sbcl-1.0.53:
   * minor incompatible changes: