From 3c1d7163688813a89ae287a6609ec435bc623e4d Mon Sep 17 00:00:00 2001 From: Christophe Rhodes Date: Fri, 26 Jul 2002 10:03:39 +0000 Subject: [PATCH] 0.7.6.8: Final deletion of %DETECT-STACK-EXHAUSTION, as per APD sbcl-devel 2002-07-26 ... delete export of %D-S-E ... increase fasl file version number Minor BUGS cleanup and cross-referencing --- BUGS | 24 ++++++++++-------------- package-data-list.lisp-expr | 2 +- src/code/early-fasl.lisp | 4 +++- version.lisp-expr | 2 +- 4 files changed, 15 insertions(+), 17 deletions(-) diff --git a/BUGS b/BUGS index 58bd328..a0bd34a 100644 --- a/BUGS +++ b/BUGS @@ -89,6 +89,9 @@ WORKAROUND: also unstable in several ways, including its inability to really grok function declarations. + As of sbcl-0.7.5, sbcl's cross-compiler does run with + *TYPE-SYSTEM-INITIALIZED*; however, this bug remains. + 7: The "compiling top-level form:" output ought to be condensed. Perhaps any number of such consecutive lines ought to turn into a @@ -1068,6 +1071,8 @@ WORKAROUND: It should be possible to be much more specific (overflow, division by zero, etc.) and of course the "How can this be?" should be fixable. + See also bugs #45.c and #183 + 148: In sbcl-0.7.1.3 on x86, COMPILE-FILE on the file (in-package :cl-user) @@ -1113,18 +1118,6 @@ WORKAROUND: Is (1 . 1) of type CONS a cons? => NIL without signalling an error. -154: - There's some sort of problem with aborting back out of the debugger - after a %DETECT-STACK-EXHAUSTION error in sbcl-0.7.1.38. In some cases - telling the debugger to ABORT doesn't get you back to the main REPL, - but instead just gives you another stack exhaustion error. The problem - doesn't occur in the trivial case - * (defun frob () (frob) (frob)) - FROB - * (frob) - but it has happened in more complicated cases (which I haven't - figured out how to reproduce). - 157: Functions SUBTYPEP, TYPEP, UPGRADED-ARRAY-ELEMENT-TYPE, and UPGRADED-COMPLEX-PART-TYPE should have an optional environment argument. @@ -1450,8 +1443,11 @@ WORKAROUND: (INTEGER 1296 1296) ...)>)[:EXTERNAL] -(189: "ignored NOTINLINE for functions defined by FLET or LABELS") - (fixed in sbcl-0.7.6.3) +190: "PPC/Linux pipe? buffer? bug" + In sbcl-0.7.6, the run-program.test.sh test script sometimes hangs + on the PPC/Linux platform, waiting for a zombie env process. This + is a classic symptom of buffer filling and deadlock, but it seems + only sporadically reproducible. DEFUNCT CATEGORIES OF BUGS IR1-#: diff --git a/package-data-list.lisp-expr b/package-data-list.lisp-expr index 5e06b46..419f0ef 100644 --- a/package-data-list.lisp-expr +++ b/package-data-list.lisp-expr @@ -924,7 +924,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries." "%CALLER-FRAME-AND-PC" "%CHECK-BOUND" "%CLOSURE-FUN" "%CLOSURE-INDEX-REF" "%COS" "%COS-QUICK" "%COSH" "%DATA-VECTOR-AND-INDEX" - "%DEPOSIT-FIELD" "%DETECT-STACK-EXHAUSTION" + "%DEPOSIT-FIELD" "%DOUBLE-FLOAT" "%DPB" "%EXP" "%EXPM1" "%FIND-POSITION" "%FIND-POSITION-VECTOR-MACRO" "%FIND-POSITION-IF" "%FIND-POSITION-IF-VECTOR-MACRO" diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp index 4520f83..db9607e 100644 --- a/src/code/early-fasl.lisp +++ b/src/code/early-fasl.lisp @@ -42,7 +42,7 @@ ;;; versions which break binary compatibility. But it certainly should ;;; be incremented for release versions which break binary ;;; compatibility. -(def!constant +fasl-file-version+ 29) +(def!constant +fasl-file-version+ 30) ;;; (record of versions before 0.7.0 deleted in 0.7.1.41) ;;; 23 = sbcl-0.7.0.1 deleted no-longer-used EVAL-STACK stuff, ;;; causing changes in *STATIC-SYMBOLS*. @@ -55,6 +55,8 @@ ;;; 28: (2002-05-08) new convention for foreign symbols to support ;;; dynamic loading in OpenBSD ;;; 29: (2002-06-24) removed *!INITIAL-FDEFN-OBJECTS* from static symbols +;;; 30: (2002-07-26) deleted all references to %DETECT-STACK-EXHAUSTION, +;;; which was introduced in version 25 ;;; 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 a650219..c3aabbb 100644 --- a/version.lisp-expr +++ b/version.lisp-expr @@ -18,4 +18,4 @@ ;;; for internal versions, especially for internal versions off the ;;; main CVS branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".) -"0.7.6.7" +"0.7.6.8" -- 1.7.10.4