0.7.6.10:

[sbcl.git] / BUGS

diff --git a/BUGS b/BUGS
index b53b355..8334a70 100644 (file)
--- 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.
@@ -1319,12 +1312,6 @@ WORKAROUND:
   the compiler handle the error, convert it into a COMPILER-ERROR, and
   continue compiling) which seems wrong.
 
-182: "SPARC/Linux floating point"
-  Evaluating (/ 1.0 0.0) at the prompt causes a Bus error and complete
-  death of the environment. Other floating point operations sometimes
-  return infinities when they should raise traps (e.g. the test case
-  for bug #146, (expt 2.0 12777)).
-
 183: "IEEE floating point issues"
   Even where floating point handling is being dealt with relatively
   well (as of sbcl-0.7.5, on sparc/sunos and alpha; see bug #146), the
@@ -1422,7 +1409,9 @@ WORKAROUND:
       (sb-c::%dvai v i))
 
 188: "compiler performance fiasco involving type inference and UNION-TYPE"
-  In sbcl-0.7.5.11 on a 700 MHz Pentium III, 
+  (In sbcl-0.7.6.10, DEFTRANSFORM CONCATENATE was commented out until this
+  bug could be fixed properly, so you won't see the bug unless you restore
+  the DEFTRANSFORM by hand.) In sbcl-0.7.5.11 on a 700 MHz Pentium III, 
     (time (compile
            nil
            '(lambda ()
@@ -1456,17 +1445,11 @@ WORKAROUND:
            (INTEGER 1296 1296)
            ...)>)[:EXTERNAL]
 
-189: "ignored NOTINLINE for functions defined by FLET or LABELS"
-  According to the ANSI definition of the NOTINLINE declaration, 
-    NOTINLINE specifies that it is undesirable to compile the functions
-    named by FUNCTION-NAMES in-line. A compiler is not free to ignore
-    this declaration; calls to the specified functions must be implemented
-    as out-of-line subroutine calls. 
-  However, as of sbcl-0.7.5.22, Python ignores this declaration for 
-  functions defined by LABELS and FLET, and merrily optimizes away the
-  LAMBDAs. (This is an annoyance not just for language lawyers, but for
-  people who want a useful BACKTRACE for functions which, for whatever
-  reason, are constrained to be implemented as LABELS or LET.)
+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-#: