X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=BUGS;h=9e778d1e9460b71253245a8b95d279f740a4008a;hb=d01a6883a21ee073c1a00c401c12185dbd2a8133;hp=55bb75401e83e04c09f9de8cdd045e92fc3e4b9b;hpb=71766d9db05e93567cb7e829abfc675c3cb895c9;p=sbcl.git

diff --git a/BUGS b/BUGS
index 55bb754..9e778d1 100644
--- a/BUGS
+++ b/BUGS
@@ -1788,7 +1788,69 @@ WORKAROUND:
   implementation of read circularity, using a symbol as a marker for
   the previously-referenced object.
 
-411: NAN issues on x86-64
-  Test :NAN-COMPARISONS in float.pure.lisp fails on x86-64, and has been
-  disabled on those platforms. Since x86 does not exhibit any problems
-  the problem is probably with the new FP implementation.
+413: type-errors in ROOM
+
+  (defvar *a* (make-array (expt 2 27)))
+  (room)
+
+  Causes a type-error on 32bit SBCL, as various byte-counts in ROOM
+  implementation overrun fixnums. 
+
+  This was fixed in 1.0.4.89, but the patch was reverted as it caused
+  ROOM to cons sufficiently to make running it in a loop deadly on
+  GENCGC: newly allocated objects survived to generation 1, where next
+  call to ROOM would see them, and allocate even more...
+
+  Reported by Faré Rideau on sbcl-devel.
+
+414: strange DISASSEMBLE warning
+
+  Compiling and disassembling 
+
+   (defun disassemble-source-form-bug (x y z)
+     (declare (optimize debug))
+     (list x y z))
+
+  Gives
+
+   WARNING: bogus form-number in form!  The source file has probably 
+   been changed too much to cope with.
+
+415: Issues creating large arrays on x86-64/Linux and x86/Darwin
+
+   (make-array (1- array-dimension-limit))
+
+   causes a GC invariant violation on x86-64/Linux, and
+   an unhandled SIGILL on x86/Darwin.
+
+416: backtrace confusion
+
+  (defun foo (x)
+    (let ((v "foo"))
+      (flet ((bar (z)
+               (oops v z)
+               (oops z v)))
+        (bar x)
+        (bar v))))
+  (foo 13)
+
+  gives the correct error, but the backtrace shows 
+    1: (SB-KERNEL:FDEFINITION-OBJECT 13 NIL)
+  as the second frame.
+
+417: Toplevel NIL expressions mess up unreachable code reporting.
+	In sbcl-1.0.10.7, COMPILE-FILE on the file
+		nil
+		(defmethod frob ((package package) stream)
+		  (if (string= (package-name package) "FOO")
+		      (pprint-logical-block (stream nil))
+		      (print-unreadable-object (package stream))))
+	causes complaints like
+		; in: SOME SB-C::STRANGE SB-C::PLACE
+		;     (SB-C::UNABLE SB-C::TO SB-C::LOCATE SB-C::SOURCE)
+		; 
+		; note: deleting unreachable code
+		; 
+		; note: deleting unreachable code
+	Deleting the toplevel NIL, or even replacing it with 3,
+	causes the system not to complain.