1.0.37.67: Reset a toplevel INLINE declaration for READ-BYTE

 * It used to remain declaimed inline after load.lisp.
   Report and patch by Stas Boukarev.

diff --git a/NEWS b/NEWS
index 23759fb..8cc7a71 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -72,6 +72,8 @@ changes relative to sbcl-1.0.37:
   * bug fix: Transforms for TRUNCATE don't die when the result is completely
     ignored anymore.
   * bug fix: Maybe restore buildability on Alpha.
+  * bug fix: READ-BYTE isn't inline anymore, fixing weird streams failures. 
+    (lp#569404)
 
 changes in sbcl-1.0.37 relative to sbcl-1.0.36:
   * enhancement: Backtrace from THROW to uncaught tag on x86oids now shows

diff --git a/src/code/load.lisp b/src/code/load.lisp
index 97258b3..3b2a82f 100644 (file)
--- a/src/code/load.lisp
+++ b/src/code/load.lisp
@@ -456,6 +456,8 @@
         ;; that this would go away?
         (fill *current-fop-table* nil))))
   t)
+
+(declaim (notinline read-byte)) ; Why is it even *declaimed* inline above?
 \f
 ;;;; stuff for debugging/tuning by collecting statistics on FOPs (?)
 

diff --git a/version.lisp-expr b/version.lisp-expr
index ef5524a..9d21537 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.37.66"
+"1.0.37.67"