X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=BUGS;h=503fdc4e43b501ee80713c32e58f5dd8c060625d;hb=3ca67be9529e3f2800facea80903062af79f870f;hp=a375a314b74d3e09faba370010777ea5fabb70fc;hpb=2419deec84b45d81610dc8d3db610c3e2f7b9486;p=sbcl.git diff --git a/BUGS b/BUGS index a375a31..503fdc4 100644 --- a/BUGS +++ b/BUGS @@ -249,20 +249,17 @@ WORKAROUND: comfortable merging the patches in the CVS version of SBCL. 108: - (TIME (ROOM T)) reports more than 200 Mbytes consed even for - a clean, just-started SBCL system. And it seems to be right: - (ROOM T) can bring a small computer to its knees for a *long* - time trying to GC afterwards. Surely there's some more economical - way to implement (ROOM T). + ROOM issues: - Daniel Barlow doesn't know what fixed this, but observes that it - doesn't seem to be the case in 0.8.7.3 any more. Instead, (ROOM T) - in a fresh SBCL causes + a) ROOM works by walking over the heap linearly, instead of + following the object graph. Hence, it report garbage objects that + are unreachable. (Maybe this is a feature and not a bug?) - debugger invoked on a SB-INT:BUG in thread 5911: - failed AVER: "(SAP= CURRENT END)" - - unless a GC has happened beforehand. + b) ROOM uses MAP-ALLOCATED-OBJECTS to walk the heap, which doesn't + check all pointers as well as it should, and can hence become + confused, leading to aver failures. As of 1.0.13.21 these (the + SAP= aver in particular) should be mostly under control, but push + ROOM hard enough and it still might croak. 117: When the compiler inline expands functions, it may be that different @@ -1803,19 +1800,6 @@ WORKAROUND: 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)) @@ -1838,23 +1822,6 @@ WORKAROUND: 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. - 418: SUBSEQ on lists doesn't support bignum indexes LIST-SUBSEQ* now has all the works necessary to support bignum indexes, @@ -1862,3 +1829,84 @@ WORKAROUND: performance elsewhere. Other generic sequence functions have this problem as well. + +419: stack-allocated indirect closure variables are not popped + + (locally (declare (optimize speed (safety 0))) + (defun bug419 (x) + (multiple-value-call #'list + (eval '(values 1 2 3)) + (let ((x x)) + (declare (dynamic-extent x)) + (flet ((mget (y) + (+ x y)) + (mset (z) + (incf x z))) + (declare (dynamic-extent #'mget #'mset)) + ((lambda (f g) (eval `(progn ,f ,g (values 4 5 6)))) #'mget #'mset)))))) + + (ASSERT (EQUAL (BUG419) '(1 2 3 4 5 6))) => failure + +420: The MISC.556 test from gcl/ansi-tests/misc.lsp fails hard. + +In sbcl-1.0.13 on Linux/x86, executing + (FUNCALL + (COMPILE NIL + '(LAMBDA (P1 P2) + (DECLARE + (OPTIMIZE (SPEED 1) (SAFETY 0) (DEBUG 0) (SPACE 0)) + (TYPE (MEMBER 8174.8604) P1) (TYPE (MEMBER -95195347) P2)) + (FLOOR P1 P2))) + 8174.8604 -95195347) +interactively causes + SB-SYS:MEMORY-FAULT-ERROR: Unhandled memory fault at #x8. +The gcl/ansi-tests/doit.lisp program terminates prematurely shortly after +MISC.556 by falling into gdb with + fatal error encountered in SBCL pid 2827: Unhandled SIGILL +unless the MISC.556 test is commented out. + +Analysis: + and a number of other arithmetic functions exhibit the +same behaviour. Here's the underlying problem: On x86 we perform +single-float + integer normally using double-precision, and then +coerce the result back to single-float. (The FILD instruction always +gives us a double-float, and unless we do MOVE-FROM-SINGLE it remains +one. Or so it seems to me, and that would also explain the observed +behaviour below.) + +During IR1 we derive the types for both + + (+ ) ; uses double-precision + (+ (FLOAT )) ; uses single-precision + +and get a mismatch for a number of unlucky arguments. This leads to +derived result type NIL, and ends up flushing the whole whole +operation -- and finally we generate code without a return sequence, +and fall through to whatever. + +The use of double-precision in the first case appears to be an +(un)happy accident -- interval arithmetic gives us the +double-precision result because that's what the backend does. + + (+ 8172.0 (coerce -95195347 'single-float)) ; => -9.518717e7 + (+ 8172.0 -95195347) ; => -9.5187176e7 + (coerce (+ 8172.0 (coerce -95195347 'double-float)) 'single-float) + ; => -9.5187176e7 + +Which should be fixed, the IR1, or the backend? + +421: READ-CHAR-NO-HANG misbehaviour on Windows Console: + + It seems that on Windows READ-CHAR-NO-HANG hangs if the user + has pressed a key, but not yet enter (ie. SYSREAD-MAY-BLOCK-P + seems to lie if the OS is buffering input for us on Console.) + + reported by Elliot Slaughter on sbcl-devel 2008/1/10. + +422: out-of-extent return not checked in safe code + + (declaim (optimize safety)) + (funcall (catch 't (block nil (throw 't (lambda () (return)))))) + +behaves ...erratically. Reported by Kevin Reid on sbcl-devel +2007-07-06. (We don't _have_ to check things like this, but we +generally try to check returns in safe code, so we should here too.)