From 224466fab9dc4e8b3faf13a121f827f198811bf6 Mon Sep 17 00:00:00 2001 From: William Harold Newman Date: Thu, 2 Oct 2003 19:04:22 +0000 Subject: [PATCH] 0.8.4: release, tagged as sbcl_0_8_4 --- CREDITS | 10 ++++------ NEWS | 32 ++++++++++++++++++-------------- src/code/early-fasl.lisp | 7 ++++++- version.lisp-expr | 2 +- 4 files changed, 29 insertions(+), 22 deletions(-) diff --git a/CREDITS b/CREDITS index 0318e38..f41a1f3 100644 --- a/CREDITS +++ b/CREDITS @@ -536,16 +536,14 @@ Douglas Crosher: handling of the CONS type to allow ANSI-style (CONS FOO BAR) types. Alexey Dejneka: - He has fixed many, many bugs. There's no single summary theme, but - he's fixed about a dozen different bugs in LOOP alone, and more - in the compiler itself. It appears that a lot of his fixes there - and elsewhere reflect systematic public-spiritedness, fixing bugs - as they show up in sbcl-devel or as archived in the BUGS file. + He fixed many, many bugs on various themes, and has done a + tremendous amount of work on the compiler in particular, fixing + bugs and refactoring. Paul Dietz He is in the process of writing a comprehensive test suite for the requirements of the ANSI Common Lisp standard. Already, at the - halfway stage, it has caught many tens of bugs in SBCL, and provided + halfway stage, it has caught hundreds of bugs in SBCL, and provided simple test cases for them. Miles Egan diff --git a/NEWS b/NEWS index 3c801ad..06c04a0 100644 --- a/NEWS +++ b/NEWS @@ -2031,8 +2031,8 @@ changes in sbcl-0.8.4 relative to sbcl-0.8.3: * fixed bug 285: TRUNCATE on bignum arguments, and indeed bignum arithmetic in general, is now much more reliable on the PPC platform. - * bug fix: LOGCOUNT on (UNSIGNED-BYTE 64) objects on the Alpha platform - now returs the right answer. + * bug fix: LOGCOUNT on (UNSIGNED-BYTE 64) objects on the Alpha + platform now returns the right answer. * optimization: restored some effective method precomputation in CLOS (turned off by an ANSI fix in sbcl-0.8.3); the amount of precomputation is now tunable. @@ -2054,18 +2054,18 @@ changes in sbcl-0.8.4 relative to sbcl-0.8.3: MEMBER-types to numeric. * bug fix: COMPILE-FILE must bind *READTABLE*. (reported by Doug McNaught) - * bug fix: (SETF AREF) on byte-sized-element arrays with constant index - argument now works properly on the Alpha platform. + * bug fix: (SETF AREF) on byte-sized-element arrays with constant + index argument now works properly on the Alpha platform. * bug fix: floating point exception treatment on the Alpha platform is improved. - * bug fix: FILE-POSITION works much better on string input and output - streams. (thanks to Nikodemus Siivola) + * bug fix: FILE-POSITION works much better on string input and + output streams. (thanks to Nikodemus Siivola) * bug fix: many threading/garbage collection symptoms sorted. - SB-THREAD:INTERRUPT-THREAD now safe to call on a thread that might - be pseudo-atomic - * internal change: Stopping for GC is now done with signals not ptrace. - GC is now done in whichever thread wanted it, instead of in the parent. - This permits a + SB-THREAD:INTERRUPT-THREAD now safe to call on a thread that + might be pseudo-atomic. + * internal change: Stopping for GC is now done with signals not + ptrace. GC is now done in whichever thread wanted it, instead of + in the parent. * bug fix: GC hooks (missing since 0.8) reinstated, so finalizers work again. * bug fix: result form in DO is not contained in the implicit @@ -2075,8 +2075,8 @@ changes in sbcl-0.8.4 relative to sbcl-0.8.3: renamed (e.g. SB-C::CONTINUATION-TYPE has become SB-C::LVAR-TYPE). * added type deriver for ISQRT (thanks to Robert E. Brown). * bug fix: better support for loading from the command line when an - initialization file sets (READTABLE-CASE *READTABLE*). (thanks to - Adam Warner) + initialization file sets (READTABLE-CASE *READTABLE*). (thanks + to Adam Warner) * fixed some bugs revealed by Paul Dietz' test suite: ** the RETURN clause in LOOP is now equivalent to DO (RETURN ...). ** ROUND and FROUND now give the right answer when given very @@ -2101,7 +2101,11 @@ changes in sbcl-0.8.4 relative to sbcl-0.8.3: an error during type derivation. ** bignum multiplication on the Alpha platform now returns the right answer. - * builds on SuSE AMD64, although still generates a 32-bit binary. + * porting: The system now builds on SuSE AMD64, although it still + generates a 32-bit binary. + * .fasl file incompatibility: The fasl file version number has + been incremented (because of the changes to internal compiler + data structures referred to above). planned incompatible changes in 0.8.x: * (not done yet, but planned:) When the profiling interface settles diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp index 64862ea..5e331ba 100644 --- a/src/code/early-fasl.lisp +++ b/src/code/early-fasl.lisp @@ -76,7 +76,7 @@ ;;; versions which break binary compatibility. But it certainly should ;;; be incremented for release versions which break binary ;;; compatibility. -(def!constant +fasl-file-version+ 44) +(def!constant +fasl-file-version+ 45) ;;; (record of versions before 2003 deleted in 2003-04-26/0.pre8.107 or so) ;;; 38: (2003-01-05) changed names of internal SORT machinery ;;; 39: (2003-02-20) in 0.7.12.1 a slot was added to @@ -95,6 +95,11 @@ ;;; I think I renumbered everything again ;;; simple-array-unsigned-byte-7, probably ;;; (thanks to pfdietz) +;;; 45: (2003-10-02) I (WHN) incremented the version for the 0.8.4 +;;; release because I couldn't immediately convince myself that +;;; .fasl files could never possibly ever refer to the SB-C +;;; CONTINUATION-related data types which were changed +;;; incompatibly in 0.8.3.62. ;;; the conventional file extension for our fasl files (declaim (type simple-string *fasl-file-type*)) diff --git a/version.lisp-expr b/version.lisp-expr index 6942537..bc8ad3b 100644 --- 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".) -"0.8.3.95" +"0.8.4" -- 1.7.10.4