X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=BUGS;h=d9e91f41cdf3948e66ac046d5f2a034273400cf4;hb=e1ba5a0d68ff8d4c8e688cd6a951aea1d56b1b61;hp=a2af047e5e5a340c16421bad9a9bc42d13bdf747;hpb=56f96e77ade913d6363a3068c94e60f44ae9b3e7;p=sbcl.git diff --git a/BUGS b/BUGS index a2af047..d9e91f4 100644 --- a/BUGS +++ b/BUGS @@ -1,4 +1,4 @@ -tREPORTING BUGS +REPORTING BUGS Bugs can be reported on the help mailing list sbcl-help@lists.sourceforge.net @@ -183,7 +183,8 @@ WORKAROUND: then executing (FOO 1.5) will cause the INTEGERP case to be selected, giving bogus output a la - exactly 1.33.. + exactly 2.5 + (or (FOO 1000.5), "exactly 1001.5") This violates the "declarations are assertions" principle. According to the ANSI spec, in the section "System Class FUNCTION", this is a case of "lying to the compiler", but the lying is done @@ -276,13 +277,6 @@ WORKAROUND: 47: DEFCLASS bugs reported by Peter Van Eynde July 25, 2000: - a: (DEFCLASS FOO () (A B A)) should signal a PROGRAM-ERROR, and - doesn't. - b: (DEFCLASS FOO () (A B A) (:DEFAULT-INITARGS X A X B)) should - signal a PROGRAM-ERROR, and doesn't. - c: (DEFCLASS FOO07 NIL ((A :ALLOCATION :CLASS :ALLOCATION :CLASS))), - and other DEFCLASS forms with duplicate specifications in their - slots, should signal a PROGRAM-ERROR, and doesn't. d: (DEFGENERIC IF (X)) should signal a PROGRAM-ERROR, but instead causes a COMPILER-ERROR. @@ -582,25 +576,6 @@ WORKAROUND: type declarations are supposed to be treated as assertions unless SAFETY 0, so we should be getting a TYPE-ERROR. -113: - reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs - collection: - (in-package :cl-user) - ;;; From: David Gadbois - ;;; - ;;; Logical pathnames aren't externalizable. - ;;; Test case: - (let ((tempfile "/tmp/test.lisp")) - (setf (logical-pathname-translations "XXX") - '(("XXX:**;*.*" "/tmp/**/*.*"))) - (with-open-file (out tempfile :direction :output) - (write-string "(defvar *path* #P\"XXX:XXX;FOO.LISP\")" out)) - (compile-file tempfile)) - The error message in sbcl-0.6.12.42 is - ; caught ERROR: - ; (while making load form for #) - ; A logical host can't be dumped as a constant: # - 115: reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs collection: @@ -672,7 +647,9 @@ WORKAROUND: (IF (NOT (IGNORE-ERRORS ..))). E.g. (defun foo1i () (if (not (ignore-errors - (make-pathname :host "foo" :directory "!bla" :name "bar"))) + (make-pathname :host "foo" + :directory "!bla" + :name "bar"))) (print "ok") (error "notunlessnot"))) The (NOT (IGNORE-ERRORS ..)) form evaluates to T, so this should be @@ -1057,11 +1034,6 @@ WORKAROUND: Since this is a reasonable user error, it shouldn't be reported as an SBCL bug. -171: - (reported by Pierre Mai while investigating bug 47): - (DEFCLASS FOO () ((A :SILLY T))) - signals a SIMPLE-ERROR, not a PROGRAM-ERROR. - 172: sbcl's treatment of at least macro lambda lists is too permissive; e.g., in sbcl-0.7.3.7: @@ -1085,19 +1057,6 @@ WORKAROUND: code. Since then the warning has been downgraded to STYLE-WARNING, so it's still a bug but at least it's a little less annoying. -174: - The error message from attempting to use a #\Return format - directive: - (format nil "~^M") ; replace "^M" with a literal #\Return - debugger invoked on condition of type SB-FORMAT::FORMAT-ERROR: - error in format: unknown format directive - ~ - ^ - is not terribly helpful; this is more noticeable than parallel cases - with e.g. #\Backspace because of the differing newline conventions - on various operating systems. (reported by Harald Hanche-Olsen on - cmucl-help 2002-05-31) - 176: reported by Alexey Dejneka 08 Jun 2002 in sbcl-devel: Playing with McCLIM, I've received an error "Unbound variable WRAPPER @@ -1310,17 +1269,9 @@ WORKAROUND: lists and &KEY arguments) do not signal errors when they should. 192: "Python treats free type declarations as promises." - a. original report by Alexey Dejneka (on sbcl-devel 2002-08-26): - (declaim (optimize (speed 0) (safety 3))) - (defun f (x) - (declare (real x)) - (+ x - (locally (declare (single-float x)) - (sin x)))) - Now (F NIL) correctly gives a type error, but (F 100) gives - a segmentation violation. - b. same fundamental problem in a different way, easy to stumble - across if you mistype and declare the wrong index in + b. What seemed like the same fundamental problem as bug 192a, but + was not fixed by the same (APD "more strict type checking + sbcl-devel 2002-08-97) patch: (DOTIMES (I ...) (DOTIMES (J ...) (DECLARE ...) ...)): (declaim (optimize (speed 1) (safety 3))) (defun trust-assertion (i) @@ -1350,13 +1301,97 @@ WORKAROUND: bad argument value is). 194: "no error from (THE REAL '(1 2 3)) in some cases" - In sbcl-0.7.7.9, - (multiple-value-prog1 (progn (the real '(1 2 3)))) - returns (1 2 3) instead of signalling an error. Also in sbcl-0.7.7.9, - a more complicated instance of this bug kept - (IGNORE-ERRORS (MIN '(1 2 3))) from returning NIL as it should when - the MIN source transform expanded to (THE REAL '(1 2 3)), because - (IGNORE-ERRORS (THE REAL '(1 2 3))) returns (1 2 3). + fixed parts: + a. In sbcl-0.7.7.9, + (multiple-value-prog1 (progn (the real '(1 2 3)))) + returns (1 2 3) instead of signalling an error. This was fixed by + APD's "more strict type checking patch", but although the fixed + code (in sbcl-0.7.7.19) works (signals TYPE-ERROR) interactively, + it's difficult to write a regression test for it, because + (IGNORE-ERRORS (MULTIPLE-VALUE-PROG1 (PROGN (THE REAL '(1 2 3))))) + still returns (1 2 3). + still-broken parts: + b. (IGNORE-ERRORS (MULTIPLE-VALUE-PROG1 (PROGN (THE REAL '(1 2 3))))) + returns (1 2 3). (As above, this shows up when writing regression + tests for fixed-ness of part a.) + c. Also in sbcl-0.7.7.9, (IGNORE-ERRORS (THE REAL '(1 2 3))) => (1 2 3). + d. At the REPL, + (null (ignore-errors + (let ((arg1 1) + (arg2 (identity (the real #(1 2 3))))) + (if (< arg1 arg2) arg1 arg2)))) + => T + but putting the same expression inside (DEFUN FOO () ...), + (FOO) => NIL. + notes: + * Actually this entry is probably multiple bugs, as + Alexey Dejneka commented on sbcl-devel 2002-09-03:) + I don't think that placing these two bugs in one entry is + a good idea: they have different explanations. The second + (min 1 nil) is caused by flushing of unused code--IDENTITY + can do nothing with it. So it is really bug 122. The first + (min nil) is due to M-V-PROG1: substituting a continuation + for the result, it forgets about type assertion. The purpose + of IDENTITY is to save the restricted continuation from + inaccurate transformations. + * Alexey Dejneka pointed out that + (IGNORE-ERRORS (IDENTITY (THE REAL '(1 2 3)))) + works as it should. Also + (IGNORE-ERRORS (VALUES (THE REAL '(1 2 3)))) + works as it should. Perhaps this is another case of VALUES type + intersections behaving in non-useful ways? + +195: "confusing reporting of not-a-REAL TYPE-ERRORs from THE REAL" + In sbcl-0.7.7.10, (THE REAL #(1 2 3)) signals a type error which + prints as "This is not a (OR SINGLE-FLOAT DOUBLE-FLOAT RATIONAL)". + The (OR SINGLE-FLOAT DOUBLE-FLOAT RATIONAL) representation of + REAL is unnecessarily confusing, especially since it relies on + internal implementation knowledge that even with SHORT-FLOAT + and LONG-FLOAT left out of the union, this type is equal to REAL. + So it'd be better just to say "This is not a REAL". + +196: "confusing error message for unREAL second arg to ATAN" + (fixed in sbcl-0.7.7.18) + +197: "failed AVER on compiling or evaluating function constants" + (reported by Antonio Martinez sbcl-devel 2002-09-12) + When compiling or evaluating function constants, such as in + (EVAL `(LAMBDA () (FUNCALL ,(LAMBDA () NIL)))) + I get the following error message: + debugger invoked on condition of type SB-INT:BUG: + failed AVER: "(LEAF-HAS-SOURCE-NAME-P LEAF)" + + Although this seems a dubious use of function constants, it would be + good either to make it work or to produce a useful error message. + +198: "conflicting THEs are not necessarily all checked" + (reported by APD sbcl-devel 2002-09-14) + (DEFUN FOO (X) + (LET (Y) + (SETF Y (THE SINGLE-FLOAT (THE INTEGER X))) + (LIST Y Y))) + + (FOO 3) => error "3 is not of type SINGLE-FLOAT" + (FOO 3F0) => (3F0 3F0) + + APD also reports that this code has not worked as intended in SBCL + since the days of sbcl-0.7.0, while CMUCL correctly detects the type + error ("is not of type NIL") for all inputs. + +199: "hairy FUNCTION types confuse the compiler" + (reported by APD sbcl-devel 2002-09-15) + (DEFUN MUR (F) + (EQ NIL (FUNCALL F))) + + (DEFUN FOO (F X) + (DECLARE (TYPE (AND FUNCTION (SATISFIES MUR)) F)) + (FUNCALL F X)) + + fails to compile, printing + failed AVER: + "(AND (EQ (IR2-CONTINUATION-PRIMITIVE-TYPE 2CONT) FUNCTION-PTYPE) (EQ CHECK T))" + + APD further reports that this bug is not present in CMUCL. DEFUNCT CATEGORIES OF BUGS IR1-#: