X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;ds=sidebyside;f=BUGS;h=cbcb818196c2f87ae199e4fb920ce44f2e81bb8d;hb=c1aa8b6b5b870f21bc8c81da85708e9d71d4eb93;hp=34cebd62c45453733e7115e1546a06df48ed1139;hpb=3b6e07c0fcb050fa86c7c42db33f49107e3097e6;p=sbcl.git diff --git a/BUGS b/BUGS index 34cebd6..cbcb818 100644 --- a/BUGS +++ b/BUGS @@ -1793,5 +1793,69 @@ WORKAROUND: disabled on those platforms. Since x86 does not exhibit any problems the problem is probably with the new FP implementation. -412: deletion of global variable references in safe code - fixed in 1.0.4.45. +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.