3 Bugs can be reported on the help mailing list
4 sbcl-help@lists.sourceforge.net
5 or on the development mailing list
6 sbcl-devel@lists.sourceforge.net
8 Please include enough information in a bug report that someone reading
9 it can reproduce the problem, i.e. don't write
10 Subject: apparent bug in PRINT-OBJECT (or *PRINT-LENGTH*?)
11 PRINT-OBJECT doesn't seem to work with *PRINT-LENGTH*. Is this a bug?
13 Subject: apparent bug in PRINT-OBJECT (or *PRINT-LENGTH*?)
14 In sbcl-1.2.3 running under OpenBSD 4.5 on my Alpha box, when
15 I compile and load the file
16 (DEFSTRUCT (FOO (:PRINT-OBJECT (LAMBDA (X Y)
17 (LET ((*PRINT-LENGTH* 4))
20 then at the command line type
22 the program loops endlessly instead of printing the object.
27 There is also some information on bugs in the manual page and
28 in the TODO file. Eventually more such information may move here.
30 The gaps in the number sequence belong to old bug descriptions which
31 have gone away (typically because they were fixed, but sometimes for
32 other reasons, e.g. because they were moved elsewhere).
35 KNOWN BUGS OF NO SPECIAL CLASS:
38 DEFSTRUCT almost certainly should overwrite the old LAYOUT information
39 instead of just punting when a contradictory structure definition
40 is loaded. As it is, if you redefine DEFSTRUCTs in a way which
41 changes their layout, you probably have to rebuild your entire
42 program, even if you know or guess enough about the internals of
43 SBCL to wager that this (undefined in ANSI) operation would be safe.
46 ANSI specifies that a type mismatch in a structure slot
47 initialization value should not cause a warning.
49 This one might not be fixed for a while because while we're big
50 believers in ANSI compatibility and all, (1) there's no obvious
51 simple way to do it (short of disabling all warnings for type
52 mismatches everywhere), and (2) there's a good portable
53 workaround. ANSI justifies this specification by saying
54 The restriction against issuing a warning for type mismatches
55 between a slot-initform and the corresponding slot's :TYPE
56 option is necessary because a slot-initform must be specified
57 in order to specify slot options; in some cases, no suitable
59 In SBCL, as in CMU CL (or, for that matter, any compiler which
60 really understands Common Lisp types) a suitable default does
61 exist, in all cases, because the compiler understands the concept
62 of functions which never return (i.e. has return type NIL, e.g.
63 ERROR). Thus, as a portable workaround, you can use a call to
64 some known-never-to-return function as the default. E.g.
66 (BAR (ERROR "missing :BAR argument")
67 :TYPE SOME-TYPE-TOO-HAIRY-TO-CONSTRUCT-AN-INSTANCE-OF))
69 (DECLAIM (FTYPE () NIL) MISSING-ARG)
70 (DEFUN REQUIRED-ARG () ; workaround for SBCL non-ANSI slot init typing
71 (ERROR "missing required argument"))
73 (BAR (REQUIRED-ARG) :TYPE TRICKY-TYPE-OF-SOME-SORT)
74 (BLETCH (REQUIRED-ARG) :TYPE TRICKY-TYPE-OF-SOME-SORT)
75 (N-REFS-SO-FAR 0 :TYPE (INTEGER 0)))
76 Such code will compile without complaint and work correctly either
77 on SBCL or on a completely compliant Common Lisp system.
80 bogus warnings about undefined functions for magic functions like
81 SB!C::%%DEFUN and SB!C::%DEFCONSTANT when cross-compiling files
82 like src/code/float.lisp. Fixing this will probably require
83 straightening out enough bootstrap consistency issues that
84 the cross-compiler can run with *TYPE-SYSTEM-INITIALIZED*.
85 Instead, the cross-compiler runs in a slightly flaky state
86 which is sane enough to compile SBCL itself, but which is
87 also unstable in several ways, including its inability
88 to really grok function declarations.
91 The "byte compiling top-level form:" output ought to be condensed.
92 Perhaps any number of such consecutive lines ought to turn into a
93 single "byte compiling top-level forms:" line.
96 The way that the compiler munges types with arguments together
97 with types with no arguments (in e.g. TYPE-EXPAND) leads to
98 weirdness visible to the user:
99 (DEFTYPE FOO () 'FIXNUM)
101 (TYPEP 11 '(FOO)) => T, which seems weird
102 (TYPEP 11 'FIXNUM) => T
103 (TYPEP 11 '(FIXNUM)) signals an error, as it should
104 The situation is complicated by the presence of Common Lisp types
105 like UNSIGNED-BYTE (which can either be used in list form or alone)
106 so I'm not 100% sure that the behavior above is actually illegal.
107 But I'm 90+% sure, and the following related behavior,
109 treating the bare symbol AND as equivalent to '(AND), is specifically
110 forbidden (by the ANSI specification of the AND type).
113 It would be nice if the
115 (during macroexpansion)
116 said what macroexpansion was at fault, e.g.
118 (during macroexpansion of IN-PACKAGE,
119 during macroexpansion of DEFFOO)
122 (SUBTYPEP '(FUNCTION (T BOOLEAN) NIL)
123 '(FUNCTION (FIXNUM FIXNUM) NIL)) => T, T
124 (Also, when this is fixed, we can enable the code in PROCLAIM which
125 checks for incompatible FTYPE redeclarations.)
128 from DTC on the CMU CL mailing list 25 Feb 2000:
129 ;;; Compiler fails when this file is compiled.
131 ;;; Problem shows up in delete-block within ir1util.lisp. The assertion
132 ;;; (assert (member (functional-kind lambda) '(:let :mv-let :assignment)))
133 ;;; fails within bind node branch.
135 ;;; Note that if c::*check-consistency* is enabled then an un-reached
136 ;;; entry is also reported.
139 (declare (values nil))
156 (let ((ttt #'(lambda () (go cccc))))
157 (declare (special ttt))
158 (return-from bbbb nil))
161 (return-from bbbb nil))))))
164 (I *think* this is a bug. It certainly seems like strange behavior. But
165 the ANSI spec is scary, dark, and deep..)
166 (FORMAT NIL "~,1G" 1.4) => "1. "
167 (FORMAT NIL "~3,1G" 1.4) => "1. "
170 from Marco Antoniotti on cmucl-imp mailing list 1 Mar 2000:
172 (setf (find-class 'ccc1) (find-class 'ccc))
173 (defmethod zut ((c ccc1)) 123)
174 DTC's recommended workaround from the mailing list 3 Mar 2000:
175 (setf (pcl::find-class 'ccc1) (pcl::find-class 'ccc))
178 The ANSI spec, in section "22.3.5.2 Tilde Less-Than-Sign: Logical Block",
179 says that an error is signalled if ~W, ~_, ~<...~:>, ~I, or ~:T is used
180 inside "~<..~>" (without the colon modifier on the closing syntax).
181 However, SBCL doesn't do this:
182 * (FORMAT T "~<munge~wegnum~>" 12)
187 Sometimes (SB-EXT:QUIT) fails with
188 Argh! maximum interrupt nesting depth (4096) exceeded, exiting
189 Process inferior-lisp exited abnormally with code 1
190 I haven't noticed a repeatable case of this yet.
193 some sort of bug in inlining and RETURN-FROM in sbcl-0.6.5: Compiling
196 (BLOCK USED-BY-SOME-Y?
199 (UNLESS (REJECTED? Y)
200 (RETURN-FROM USED-BY-SOME-Y? T)))))
201 (DECLARE (INLINE FROB))
206 error in function SB-KERNEL:ASSERT-ERROR:
207 The assertion (EQ (SB-C::CONTINUATION-KIND SB-C::CONT) :BLOCK-START) failed.
208 This is still present in sbcl-0.6.8.
211 In some cases the compiler believes type declarations on array
212 elements without checking them, e.g.
213 (DECLAIM (OPTIMIZE (SAFETY 3) (SPEED 1) (SPACE 1)))
216 (DECLARE (TYPE (SIMPLE-ARRAY CONS 1) X))
217 (WHEN (CONSP (AREF X 0))
219 (BAR (VECTOR (MAKE-FOO :A 11 :B 12)))
222 in SBCL 0.6.5 (and also in CMU CL 18b). This does not happen for
223 all cases, e.g. the type assumption *is* checked if the array
224 elements are declared to be of some structure type instead of CONS.
227 The printer doesn't report closures very well. This is true in
231 #<Closure Over Function "DEFUN STRUCTURE-SLOT-ACCESSOR" {134D1A1}>
232 It would be nice to make closures have a settable name slot,
233 and make things like DEFSTRUCT and FLET, which create closures,
234 set helpful values into this slot.
237 And as long as we're wishing, it would be awfully nice if INSPECT could
238 also report on closures, telling about the values of the bound variables.
241 The compiler assumes that any time a function of declared FTYPE
242 doesn't signal an error, its arguments were of the declared type.
243 E.g. compiling and loading
244 (DECLAIM (OPTIMIZE (SAFETY 3)))
245 (DEFUN FACTORIAL (X) (GAMMA (1+ X)))
247 (DECLAIM (FTYPE (FUNCTION (UNSIGNED-BYTE)) FACTORIAL))
249 (COND ((> (FACTORIAL X) 1.0E6)
250 (FORMAT T "too big~%"))
252 (FORMAT T "exactly ~S~%" (FACTORIAL X)))
254 (FORMAT T "approximately ~S~%" (FACTORIAL X)))))
257 will cause the INTEGERP case to be selected, giving bogus output a la
259 This violates the "declarations are assertions" principle.
260 According to the ANSI spec, in the section "System Class FUNCTION",
261 this is a case of "lying to the compiler", but the lying is done
262 by the code which calls FACTORIAL with non-UNSIGNED-BYTE arguments,
263 not by the unexpectedly general definition of FACTORIAL. In any case,
264 "declarations are assertions" means that lying to the compiler should
265 cause an error to be signalled, and should not cause a bogus
266 result to be returned. Thus, the compiler should not assume
267 that arbitrary functions check their argument types. (It might
268 make sense to add another flag (CHECKED?) to DEFKNOWN to
269 identify functions which *do* check their argument types.)
270 (Also, verify that the compiler handles declared function
271 return types as assertions.)
274 DEFMETHOD doesn't check the syntax of &REST argument lists properly,
275 accepting &REST even when it's not followed by an argument name:
276 (DEFMETHOD FOO ((X T) &REST) NIL)
279 TYPEP of VALUES types is sometimes implemented very inefficiently, e.g. in
280 (DEFTYPE INDEXOID () '(INTEGER 0 1000))
282 (DECLARE (TYPE INDEXOID X))
283 (THE (VALUES INDEXOID)
285 where the implementation of the type check in function FOO
286 includes a full call to %TYPEP. There are also some fundamental problems
287 with the interpretation of VALUES types (inherited from CMU CL, and
288 from the ANSI CL standard) as discussed on the cmucl-imp@cons.org
289 mailing list, e.g. in Robert Maclachlan's post of 21 Jun 2000.
292 The definitions of SIGCONTEXT-FLOAT-REGISTER and
293 %SET-SIGCONTEXT-FLOAT-REGISTER in x86-vm.lisp say they're not
294 supported on FreeBSD because the floating point state is not saved,
295 but at least as of FreeBSD 4.0, the floating point state *is* saved,
296 so they could be supported after all. Very likely
297 SIGCONTEXT-FLOATING-POINT-MODES could now be supported, too.
300 (as discussed by Douglas Crosher on the cmucl-imp mailing list ca.
301 Aug. 10, 2000): CMUCL currently interprets 'member as '(member); same
302 issue with 'union, 'and, 'or etc. So even though according to the
303 ANSI spec, bare 'MEMBER, 'AND, and 'OR are not legal types, CMUCL
304 (and now SBCL) interpret them as legal types.
307 ANSI specifies DEFINE-SYMBOL-MACRO, but it's not defined in SBCL.
308 CMU CL added it ca. Aug 13, 2000, after some discussion on the mailing
309 list, and it is probably possible to use substantially the same
310 patches to add it to SBCL.
313 a slew of floating-point-related errors reported by Peter Van Eynde
315 a: (fixed in sbcl-0.6.11.25)
316 b: SBCL's value for LEAST-POSITIVE-SHORT-FLOAT is bogus, and
317 should probably be 1.4012985e-45. In SBCL,
318 (/ LEAST-POSITIVE-SHORT-FLOAT 2) returns a number smaller
319 than LEAST-POSITIVE-SHORT-FLOAT. Similar problems
320 exist for LEAST-NEGATIVE-SHORT-FLOAT, LEAST-POSITIVE-LONG-FLOAT,
321 and LEAST-NEGATIVE-LONG-FLOAT.
322 c: Many expressions generate floating infinity:
327 PVE's regression tests want them to raise errors. SBCL
328 generates the infinities instead, which may or may not be
330 d: (in section12.erg) various forms a la
331 (FLOAT 1 DOUBLE-FLOAT-EPSILON)
332 don't give the right behavior.
335 type safety errors reported by Peter Van Eynde July 25, 2000:
336 a: (COERCE (QUOTE (A B C)) (QUOTE (VECTOR * 4)))
338 In general lengths of array type specifications aren't
339 checked by COERCE, so it fails when the spec is
340 (VECTOR 4), (STRING 2), (SIMPLE-BIT-VECTOR 3), or whatever.
341 b: CONCATENATE has the same problem of not checking the length
342 of specified output array types. MAKE-SEQUENCE and MAP and
343 MERGE also have the same problem.
344 c: (COERCE 'AND 'FUNCTION) returns something related to
345 (MACRO-FUNCTION 'AND), but ANSI says it should raise an error.
346 d: ELT signals SIMPLE-ERROR if its index argument
347 isn't a valid index for its sequence argument, but should
348 signal TYPE-ERROR instead.
349 e: FILE-LENGTH is supposed to signal a type error when its
350 argument is not a stream associated with a file, but doesn't.
351 f: (FLOAT-RADIX 2/3) should signal an error instead of
353 g: (LOAD "*.lsp") should signal FILE-ERROR.
354 h: (MAKE-CONCATENATED-STREAM (MAKE-STRING-OUTPUT-STREAM))
355 should signal TYPE-ERROR.
356 i: MAKE-TWO-WAY-STREAM doesn't check that its arguments can
357 be used for input and output as needed. It should fail with
358 TYPE-ERROR when handed e.g. the results of
359 MAKE-STRING-INPUT-STREAM or MAKE-STRING-OUTPUT-STREAM in
360 the inappropriate positions, but doesn't.
361 j: (PARSE-NAMESTRING (COERCE (LIST #\f #\o #\o (CODE-CHAR 0) #\4 #\8)
363 should probably signal an error instead of making a pathname with
365 k: READ-BYTE is supposed to signal TYPE-ERROR when its argument is
366 not a binary input stream, but instead cheerfully reads from
367 character streams, e.g. (MAKE-STRING-INPUT-STREAM "abc").
370 DEFCLASS bugs reported by Peter Van Eynde July 25, 2000:
371 a: (DEFCLASS FOO () (A B A)) should signal a PROGRAM-ERROR, and
373 b: (DEFCLASS FOO () (A B A) (:DEFAULT-INITARGS X A X B)) should
374 signal a PROGRAM-ERROR, and doesn't.
375 c: (DEFCLASS FOO07 NIL ((A :ALLOCATION :CLASS :ALLOCATION :CLASS))),
376 and other DEFCLASS forms with duplicate specifications in their
377 slots, should signal a PROGRAM-ERROR, and doesn't.
378 d: (DEFGENERIC IF (X)) should signal a PROGRAM-ERROR, but instead
379 causes a COMPILER-ERROR.
382 SYMBOL-MACROLET bugs reported by Peter Van Eynde July 25, 2000:
383 a: (SYMBOL-MACROLET ((T TRUE)) ..) should probably signal
384 PROGRAM-ERROR, but SBCL accepts it instead.
385 b: SYMBOL-MACROLET should refuse to bind something which is
386 declared as a global variable, signalling PROGRAM-ERROR.
387 c: SYMBOL-MACROLET should signal PROGRAM-ERROR if something
388 it binds is declared SPECIAL inside.
391 LOOP bugs reported by Peter Van Eynde July 25, 2000:
392 a: (LOOP WITH (A B) DO (PRINT 1)) is a syntax error according to
393 the definition of WITH clauses given in the ANSI spec, but
394 compiles and runs happily in SBCL.
395 b: a messy one involving package iteration:
396 interpreted Form: (LET ((PACKAGE (MAKE-PACKAGE "LOOP-TEST"))) (INTERN "blah" PACKAGE) (LET ((BLAH2 (INTERN "blah2" PACKAGE))) (EXPORT BLAH2 PACKAGE)) (LIST (SORT (LOOP FOR SYM BEING EACH PRESENT-SYMBOL OF PACKAGE FOR SYM-NAME = (SYMBOL-NAME SYM) COLLECT SYM-NAME) (FUNCTION STRING<)) (SORT (LOOP FOR SYM BEING EACH EXTERNAL-SYMBOL OF PACKAGE FOR SYM-NAME = (SYMBOL-NAME SYM) COLLECT SYM-NAME) (FUNCTION STRING<))))
397 Should be: (("blah" "blah2") ("blah2"))
398 SBCL: (("blah") ("blah2"))
399 * (LET ((X 1)) (LOOP FOR I BY (INCF X) FROM X TO 10 COLLECT I))
400 doesn't work -- SBCL's LOOP says BY isn't allowed in a FOR clause.
403 type system errors reported by Peter Van Eynde July 25, 2000:
404 a: (SUBTYPEP 'BIGNUM 'INTEGER) => NIL, NIL
405 but should be (VALUES T T) instead.
406 b: (SUBTYPEP 'EXTENDED-CHAR 'CHARACTER) => NIL, NIL
407 but should be (VALUES T T) instead.
408 c: (SUBTYPEP '(INTEGER (0) (0)) 'NIL) dies with nested errors.
409 d: In general, the system doesn't like '(INTEGER (0) (0)) -- it
410 blows up at the level of SPECIFIER-TYPE with
411 "Lower bound (0) is greater than upper bound (0)." Probably
412 SPECIFIER-TYPE should return NIL instead.
413 e: (TYPEP 0 '(COMPLEX (EQL 0)) fails with
414 "Component type for Complex is not numeric: (EQL 0)."
415 This might be easy to fix; the type system already knows
416 that (SUBTYPEP '(EQL 0) 'NUMBER) is true.
417 f: The type system doesn't know about the condition system,
418 so that e.g. (TYPEP 'SIMPLE-ERROR 'ERROR)=>NIL.
419 g: The type system isn't all that smart about relationships
420 between hairy types, as shown in the type.erg test results,
421 e.g. (SUBTYPEP 'CONS '(NOT ATOM)) => NIL, NIL.
424 miscellaneous errors reported by Peter Van Eynde July 25, 2000:
426 (DEFGENERIC FOO02 (X))
427 (DEFMETHOD FOO02 ((X NUMBER)) T)
428 (LET ((M (FIND-METHOD (FUNCTION FOO02)
430 (LIST (FIND-CLASS (QUOTE NUMBER))))))
431 (REMOVE-METHOD (FUNCTION FOO02) M)
432 (DEFGENERIC FOO03 (X))
433 (ADD-METHOD (FUNCTION FOO03) M)))
434 should give an error, but SBCL allows it.
435 b: READ should probably return READER-ERROR, not the bare
436 arithmetic error, when input a la "1/0" or "1e1000" causes
440 It has been reported (e.g. by Peter Van Eynde) that there are
441 several metaobject protocol "errors". (In order to fix them, we might
442 need to document exactly what metaobject protocol specification
443 we're following -- the current code is just inherited from PCL.)
446 another error from Peter Van Eynde 5 September 2000:
447 (FORMAT NIL "~F" "FOO") should work, but instead reports an error.
448 PVE submitted a patch to deal with this bug, but it exposes other
449 comparably serious bugs, so I didn't apply it. It looks as though
450 the FORMAT code needs a fair amount of rewriting in order to comply
451 with the various details of the ANSI spec.
454 The implementation of #'+ returns its single argument without
455 type checking, e.g. (+ "illegal") => "illegal".
458 Attempting to use COMPILE on something defined by DEFMACRO fails:
459 (DEFMACRO FOO (X) (CONS X X))
461 Error in function C::GET-LAMBDA-TO-COMPILE:
462 #<Closure Over Function "DEFUN (SETF MACRO-FUNCTION)" {480E21B1}> was defined in a non-null environment.
465 (SUBTYPEP '(AND ZILCH INTEGER) 'ZILCH) => NIL, NIL
466 Note: I looked into fixing this in 0.6.11.15, but gave up. The
467 problem seems to be that there are two relevant type methods for
468 the subtypep operation, HAIRY :COMPLEX-SUBTYPEP-ARG2 and
469 INTERSECTION :COMPLEX-SUBTYPEP-ARG1, and only the first is
470 called. This could be fixed, but type dispatch is messy and
471 confusing enough already, I don't want to complicate it further.
472 Perhaps someday we can make CLOS cross-compiled (instead of compiled
473 after bootstrapping) so that we don't need to have the type system
474 available before CLOS, and then we can rewrite the type methods to
475 CLOS methods, and then expressing the solutions to stuff like this
476 should become much more straightforward. -- WHN 2001-03-14
479 The debugger LIST-LOCATIONS command doesn't work properly.
482 Compiling and loading
483 (DEFUN FAIL (X) (THROW 'FAIL-TAG X))
485 then requesting a BACKTRACE at the debugger prompt gives no information
486 about where in the user program the problem occurred.
489 The compiler is supposed to do type inference well enough that
492 ((SIMPLE-ARRAY SINGLE-FLOAT)
494 (DECLARE (TYPE (SIMPLE-ARRAY SINGLE-FLOAT) X))
497 is redundant. However, as reported by Juan Jose Garcia Ripoll for
498 CMU CL, it sometimes doesn't. Adding declarations is a pretty good
499 workaround for the problem for now, but can't be done by the TYPECASE
500 macros themselves, since it's too hard for the macro to detect
501 assignments to the variable within the clause.
502 Note: The compiler *is* smart enough to do the type inference in
503 many cases. This case, derived from a couple of MACROEXPAND-1
504 calls on Ripoll's original test case,
506 (DECLARE (OPTIMIZE SPEED (SAFETY 0)))
507 (COND ((TYPEP A '(SIMPLE-ARRAY SINGLE-FLOAT)) NIL
508 (LET ((LENGTH (ARRAY-TOTAL-SIZE A)))
509 (LET ((I 0) (G2554 LENGTH))
510 (DECLARE (TYPE REAL G2554) (TYPE REAL I))
513 (WHEN (>= I G2554) (GO SB-LOOP::END-LOOP))
514 (SETF (ROW-MAJOR-AREF A I) (- (ROW-MAJOR-AREF A I)))
515 (GO SB-LOOP::NEXT-LOOP)
516 SB-LOOP::END-LOOP))))))
517 demonstrates the problem; but the problem goes away if the TAGBODY
518 and GO forms are removed (leaving the SETF in ordinary, non-looping
519 code), or if the TAGBODY and GO forms are retained, but the
520 assigned value becomes 0.0 instead of (- (ROW-MAJOR-AREF A I)).
523 Paul Werkowski wrote on cmucl-imp@cons.org 2000-11-15
524 I am looking into this problem that showed up on the cmucl-help
525 list. It seems to me that the "implementation specific environment
526 hacking functions" found in pcl/walker.lisp are completely messed
527 up. The good thing is that they appear to be barely used within
528 PCL and the munged environment object is passed to cmucl only
529 in calls to macroexpand-1, which is probably why this case fails.
530 SBCL uses essentially the same code, so if the environment hacking
531 is screwed up, it affects us too.
534 Using the pretty-printer from the command prompt gives funny
535 results, apparently because the pretty-printer doesn't know
536 about user's command input, including the user's carriage return
537 that the user, and therefore the pretty-printer thinks that
538 the new output block should start indented 2 or more characters
539 rightward of the correct location.
542 (probably related to bug #70; maybe related to bug #109)
543 As reported by Carl Witty on submit@bugs.debian.org 1999-05-08,
545 (in-package "CL-USER")
546 (defun equal-terms (termx termy)
548 ((alpha-equal-bound-term-lists (listx listy)
549 (or (and (null listx) (null listy))
551 (let ((bindings-x (bindings-of-bound-term (car listx)))
552 (bindings-y (bindings-of-bound-term (car listy))))
553 (if (and (null bindings-x) (null bindings-y))
554 (alpha-equal-terms (term-of-bound-term (car listx))
555 (term-of-bound-term (car listy)))
556 (and (= (length bindings-x) (length bindings-y))
558 (enter-binding-pairs (bindings-of-bound-term (car listx))
559 (bindings-of-bound-term (car listy)))
560 (alpha-equal-terms (term-of-bound-term (car listx))
561 (term-of-bound-term (car listy)))
562 (exit-binding-pairs (bindings-of-bound-term (car listx))
563 (bindings-of-bound-term (car listy)))))))
564 (alpha-equal-bound-term-lists (cdr listx) (cdr listy)))))
566 (alpha-equal-terms (termx termy)
567 (if (and (variable-p termx)
569 (equal-bindings (id-of-variable-term termx)
570 (id-of-variable-term termy))
571 (and (equal-operators-p (operator-of-term termx) (operator-of-term termy))
572 (alpha-equal-bound-term-lists (bound-terms-of-term termx)
573 (bound-terms-of-term termy))))))
577 (with-variable-invocation (alpha-equal-terms termx termy))))))
578 causes an assertion failure
579 The assertion (EQ (C::LAMBDA-TAIL-SET C::CALLER)
580 (C::LAMBDA-TAIL-SET (C::LAMBDA-HOME C::CALLEE))) failed.
582 Bob Rogers reports (1999-07-28 on cmucl-imp@cons.org) a smaller test
583 case with the same problem:
584 (defun parse-fssp-alignment ()
585 ;; Given an FSSP alignment file named by the argument . . .
586 (labels ((get-fssp-char ()
590 ;; Stub body, enough to tickle the bug.
591 (list (read-fssp-char)
595 ANSI specifies that the RESULT-TYPE argument of CONCATENATE must be
596 a subtype of SEQUENCE, but CONCATENATE doesn't check this properly:
597 (CONCATENATE 'SIMPLE-ARRAY #(1 2) '(3)) => #(1 2 3)
598 This also leads to funny behavior when derived type specifiers
599 are used, as originally reported by Milan Zamazal for CMU CL (on the
600 Debian bugs mailing list (?) 2000-02-27), then reported by Martin
601 Atzmueller for SBCL (2000-10-01 on sbcl-devel@lists.sourceforge.net):
602 (DEFTYPE FOO () 'SIMPLE-ARRAY)
603 (CONCATENATE 'FOO #(1 2) '(3))
604 => #<ARRAY-TYPE SIMPLE-ARRAY> is a bad type specifier for
606 The derived type specifier FOO should act the same way as the
607 built-in type SIMPLE-ARRAY here, but it doesn't. That problem
608 doesn't seem to exist for sequence types:
609 (DEFTYPE BAR () 'SIMPLE-VECTOR)
610 (CONCATENATE 'BAR #(1 2) '(3)) => #(1 2 3)
613 As reported by Winton Davies on a CMU CL mailing list 2000-01-10,
614 and reported for SBCL by Martin Atzmueller 2000-10-20: (TRACE GETHASH)
615 crashes SBCL. In general tracing anything which is used in the
616 implementation of TRACE is likely to have the same problem.
619 As reported by Daniel Solaz on cmucl-help@cons.org 2000-11-23,
620 SXHASH returns the same value for all non-STRUCTURE-OBJECT instances,
621 notably including all PCL instances. There's a limit to how much
622 SXHASH can do to return unique values for instances, but at least
623 it should probably look at the class name, the way that it does
624 for STRUCTURE-OBJECTs.
627 As reported by Martin Atzmueller on the sbcl-devel list 2000-11-22,
628 > There remains one issue, that is a bug in SBCL:
629 > According to my interpretation of the spec, the ":" and "@" modifiers
630 > should appear _after_ the comma-seperated arguments.
631 > Well, SBCL (and CMUCL for that matter) accept
632 > (ASSERT (STRING= (FORMAT NIL "~:8D" 1) " 1"))
633 > where the correct way (IMHO) should be
634 > (ASSERT (STRING= (FORMAT NIL "~8:D" 1) " 1"))
635 Probably SBCL should stop accepting the "~:8D"-style format arguments,
636 or at least issue a warning.
639 (probably related to bug #65; maybe related to bug #109)
640 The compiler doesn't like &OPTIONAL arguments in LABELS and FLET
642 (DEFUN FIND-BEFORE (ITEM SEQUENCE &KEY (TEST #'EQL))
643 (LABELS ((FIND-ITEM (OBJ SEQ TEST &OPTIONAL (VAL NIL))
644 (LET ((ITEM (FIRST SEQ)))
647 ((FUNCALL TEST OBJ ITEM)
650 (FIND-ITEM OBJ (REST SEQ) TEST (NCONC VAL `(,ITEM))))))))
651 (FIND-ITEM ITEM SEQUENCE TEST)))
652 from David Young's bug report on cmucl-help@cons.org 30 Nov 2000
653 causes sbcl-0.6.9 to fail with
654 error in function SB-KERNEL:ASSERT-ERROR:
655 The assertion (EQ (SB-C::LAMBDA-TAIL-SET SB-C::CALLER)
656 (SB-C::LAMBDA-TAIL-SET
657 (SB-C::LAMBDA-HOME SB-C::CALLEE))) failed.
660 (DECLAIM (OPTIMIZE ..)) doesn't work. E.g. even after
661 (DECLAIM (OPTIMIZE (SPEED 3))), things are still optimized with
662 the previous SPEED policy. This bug will probably get fixed in
663 0.6.9.x in a general cleanup of optimization policy.
666 (DECLAIM (OPTIMIZE ..)) doesn't work properly inside LOCALLY forms.
669 As noted in the ANSI specification for COERCE, (COERCE 3 'COMPLEX)
670 gives a result which isn't COMPLEX. The result type optimizer
671 for COERCE doesn't know this, perhaps because it was written before
672 ANSI threw this curveball: the optimizer thinks that COERCE always
673 returns a result of the specified type. Thus while the interpreted
675 (DEFUN TRICKY (X) (TYPEP (COERCE X 'COMPLEX) 'COMPLEX))
676 returns the correct result,
678 the compiled function
684 As reported by Martin Atzmueller on sbcl-devel 26 Dec 2000,
685 ANSI says that WITH-OUTPUT-TO-STRING should have a keyword
686 :ELEMENT-TYPE, but in sbcl-0.6.9 this is not defined for
687 WITH-OUTPUT-TO-STRING.
690 ANSI says in one place that type declarations can be abbreviated even
691 when the type name is not a symbol, e.g.
692 (DECLAIM ((VECTOR T) *FOOVECTOR*))
693 SBCL doesn't support this. But ANSI says in another place that this
694 isn't allowed. So it's not clear this is a bug after all. (See the
695 e-mail on cmucl-help@cons.org on 2001-01-16 and 2001-01-17 from WHN
699 as pointed out by Dan Barlow on sbcl-devel 2000-07-02:
700 The PICK-TEMPORARY-FILE-NAME utility used by LOAD-FOREIGN uses
701 an easily guessable temporary filename in a way which might open
702 applications using LOAD-FOREIGN to hijacking by malicious users
703 on the same machine. Incantations for doing this safely are
704 floating around the net in various "how to write secure programs
705 despite Unix" documents, and it would be good to (1) fix this in
706 LOAD-FOREIGN, and (2) hunt for any other code which uses temporary
707 files and make it share the same new safe logic.
710 (fixed early Feb 2001 by MNA)
713 As reported by wbuss@TELDA.NET (Wolfhard Buss) on cmucl-help
716 (loop with (a . b) of-type float = '(0.0 . 1.0)
717 and (c . d) of-type float = '(2.0 . 3.0)
718 return (list a b c d))
719 should evaluate to (0.0 1.0 2.0 3.0). cmucl-18c disagrees and
720 invokes the debugger: "B is not of type list".
721 SBCL does the same thing.
724 Functions are assigned names based on the context in which they're
725 defined. This is less than ideal for the functions which are
726 used to implement CLOS methods. E.g. the output of
727 (DESCRIBE 'PRINT-OBJECT) lists functions like
728 #<FUNCTION "DEF!STRUCT (TRACE-INFO (:MAKE-LOAD-FORM-FUN SB-KERNEL:JUST-DUMP-IT-NORMALLY) (:PRINT-OBJECT #))" {1020E49}>
730 #<FUNCTION "MACROLET ((FORCE-DELAYED-DEF!METHODS NIL #))" {1242871}>
731 It would be better if these functions' names always identified
732 them as methods, and identified their generic functions and
736 RANDOM-INTEGER-EXTRA-BITS=10 may not be large enough for the RANDOM
737 RNG to be high quality near RANDOM-FIXNUM-MAX; it looks as though
738 the mean of the distribution can be systematically O(0.1%) wrong.
739 Just increasing R-I-E-B is probably not a good solution, since
740 it would decrease efficiency more than is probably necessary. Perhaps
741 using some sort of accept/reject method would be better.
744 (SUBTYPEP '(SATISFIES SOME-UNDEFINED-FUN) NIL)=>NIL,T (should be NIL,NIL)
747 Internally the compiler sometimes evaluates
748 (sb-kernel:type/= (specifier-type '*) (specifier-type t))
749 (I stumbled across this when I added an
750 (assert (not (eq type1 *wild-type*)))
751 in the NAMED :SIMPLE-= type method.) '* isn't really a type, and
752 in a type context should probably be translated to T, and so it's
753 probably to ask whether it's equal to the T type and then (using the
754 EQ type comparison in the NAMED :SIMPLE-= type method) return NIL.
755 (I haven't tried to investigate this bug enough to guess whether
756 there might be any user-level symptoms.)
759 a latent cross-compilation/bootstrapping bug: The cross-compilation
760 host's CL:CHAR-CODE-LIMIT is used in target code in readtable.lisp
761 and possibly elsewhere. Instead, we should use the target system's
762 CHAR-CODE-LIMIT. This will probably cause problems if we try to
763 bootstrap on a system which uses a different value of CHAR-CODE-LIMIT
767 (subtypep '(or (integer -1 1)
771 (integer -1 1))) => NIL,T
772 An analogous problem with SINGLE-FLOAT and REAL types was fixed in
773 sbcl-0.6.11.22, but some peculiarites of the RATIO type make it
774 awkward to generalize the fix to INTEGER and RATIONAL. It's not
775 clear what's the best fix. (See the "bug in type handling" discussion
776 on cmucl-imp ca. 2001-03-22 and ca. 2001-02-12.)
779 In sbcl-0.6.11.26, (COMPILE 'IN-HOST-COMPILATION-MODE) in
780 src/cold/shared.lisp doesn't correctly translate the
782 (defun in-host-compilation-mode (fn)
783 (let ((*features* (cons :sb-xc-host *features*))
784 ;; the CROSS-FLOAT-INFINITY-KLUDGE, as documented in
785 ;; base-target-features.lisp-expr:
786 (*shebang-features* (set-difference *shebang-features*
787 '(:sb-propagate-float-type
788 :sb-propagate-fun-type))))
789 (with-additional-nickname ("SB-XC" "SB!XC")
791 No error is reported by the compiler, but when the function is executed,
793 TYPE-ERROR in SB-KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:
794 (:LINUX :X86 :IEEE-FLOATING-POINT :SB-CONSTRAIN-FLOAT-TYPE :SB-TEST
795 :SB-INTERPRETER :SB-DOC :UNIX ...) is not of type SYMBOL.
798 Inconsistencies between derived and declared VALUES return types for
799 DEFUN aren't checked very well. E.g. the logic which successfully
800 catches problems like
801 (declaim (ftype (function (fixnum) float) foo))
803 (declare (type integer x))
804 (values x)) ; wrong return type, detected, gives warning, good!
806 (declaim (ftype (function (t) (values t t)) bar))
808 (values x)) ; wrong number of return values, no warning, bad!
809 The cause of this is seems to be that (1) the internal function
810 VALUES-TYPES-EQUAL-OR-INTERSECT used to make the check handles its
811 arguments symmetrically, and (2) when the type checking code was
812 written back when when SBCL's code was still CMU CL, the intent
814 (declaim (ftype (function (t) t) bar))
816 (values x x)) ; wrong number of return values; should give warning?
817 not be warned for, because a two-valued return value is considered
818 to be compatible with callers who expects a single value to be
819 returned. That intent is probably not appropriate for modern ANSI
820 Common Lisp, but fixing this might be complicated because of other
821 divergences between auld-style and new-style handling of
822 multiple-VALUES types. (Some issues related to this were discussed
823 on cmucl-imp at some length sometime in 2000.)
826 The facility for dumping a running Lisp image to disk gets confused
827 when run without the PURIFY option, and creates an unnecessarily large
828 core file (apparently representing memory usage up to the previous
829 high-water mark). Moreover, when the file is loaded, it confuses the
830 GC, so that thereafter memory usage can never be reduced below that
834 The TRACE facility can't be used on some kinds of functions.
835 (Basically, the breakpoint facility was incompletely implemented
836 in the X86 port of CMU CL, and hasn't been fixed in SBCL.)
839 In sbcl-0.6.11.41 (and in all earlier SBCL, and in CMU
840 CL), out-of-line structure slot setters are horribly inefficient
841 whenever the type of the slot is declared, because out-of-line
842 structure slot setters are implemented as closures to save space,
843 so the compiler doesn't compile the type test into code, but
844 instead just saves the type in a lexical closure and interprets it
846 A proper solution involves deciding whether it's really worth
847 saving space by implementing structure slot accessors as closures.
848 (If it's not worth it, the problem vanishes automatically. If it
849 is worth it, there are hacks we could use to force type tests to
850 be compiled anyway, and even shared. E.g. we could implement
851 an EQUAL hash table mapping from types to compiled type tests,
852 and save the appropriate compiled type test as part of each lexical
853 closure; or we could make the lexical closures be placeholders
854 which overwrite their old definition as a lexical closure with
855 a new compiled definition the first time that they're called.)
856 As a workaround for the problem, #'(SETF FOO) expressions can
857 be replaced with (EFFICIENT-SETF-FUNCTION FOO), where
858 (defmacro efficient-setf-function (place-function-name)
859 (or #+sbcl (and (sb-impl::info :function :accessor-for place-function-name)
860 ;; a workaround for the problem, encouraging the
861 ;; inline expansion of the structure accessor, so
862 ;; that the compiler can optimize its type test
863 (let ((new-value (gensym "NEW-VALUE-"))
864 (structure-value (gensym "STRUCTURE-VALUE-")))
865 `(lambda (,new-value ,structure-value)
866 (setf (,place-function-name ,structure-value)
868 ;; no problem, can just use the ordinary expansion
869 `(function (setf ,place-function-name))))
872 DESCRIBE interacts poorly with *PRINT-CIRCLE*, e.g. the output from
873 (let ((*print-circle* t)) (describe (make-hash-table)))
875 #<HASH-TABLE :TEST EQL :COUNT 0 {90BBFC5}> is an . (EQL)
877 Its REHASH-SIZE is 1.5. Its REHASH-THRESHOLD is . (1.0)
878 It holds 0 key/value pairs.
879 where the ". (EQL)" and ". (1.0)" substrings are screwups.
880 (This is likely a pretty-printer problem which happens to
881 be exercised by DESCRIBE, not actually a DESCRIBE problem.)
884 There's apparently a bug in CEILING optimization which caused
885 Douglas Crosher to patch the CMU CL version. Martin Atzmueller
886 applied the patches to SBCL and they didn't seem to cause problems
887 (as reported sbcl-devel 2001-05-04). However, since the patches
888 modify nontrivial code which was apparently written incorrectly
889 the first time around, until regression tests are written I'm not
890 comfortable merging the patches in the CVS version of SBCL.
893 The error message for calls to structure accessors with the
894 wrong number of arguments is confusing and of the wrong
895 condition class (TYPE-ERROR instead of PROGRAM-ERROR):
896 * (defstruct foo x y)
898 debugger invoked on condition of type SIMPLE-TYPE-ERROR:
899 Structure for accessor FOO-X is not a FOO:
903 As reported by Arthur Lemmens sbcl-devel 2001-05-05, ANSI
904 requires that SYMBOL-MACROLET refuse to rebind special variables,
905 but SBCL doesn't do this. (Also as reported by AL in the same
906 message, SBCL depended on this nonconforming behavior to build
907 itself, because of the way that **CURRENT-SEGMENT** was implemented.
908 As of sbcl-0.6.12.x, this dependence on the nonconforming behavior
909 has been fixed, but the nonconforming behavior remains.)
912 As reported by Arthur Lemmens sbcl-devel 2001-05-05, ANSI's
913 definition of (LOOP .. DO ..) requires that the terms following
914 DO all be compound forms. SBCL's implementation of LOOP allows
915 non-compound forms (like the bare symbol COUNT, in his example)
919 (DESCRIBE 'SB-ALIEN:DEF-ALIEN-TYPE) reports the macro argument list
923 in #<PACKAGE "SB-ALIEN">.
924 Macro-function: #<FUNCTION "DEF!MACRO DEF-ALIEN-TYPE" {19F4A39}>
925 Macro arguments: (#:whole-470 #:environment-471)
926 On Sat, May 26, 2001 09:45:57 AM CDT it was compiled from:
927 /usr/stuff/sbcl/src/code/host-alieneval.lisp
928 Created: Monday, March 12, 2001 07:47:43 AM CST
931 (DESCRIBE 'STREAM-READ-BYTE)
934 (reported by Eric Marsden on cmucl-imp 2001-06-15)
936 (TYPEP 0 '(COMPLEX (EQL 0)))
937 signals an error in sbcl-0.6.12.34,
938 The component type for COMPLEX is not numeric: (EQL 0)
939 This is funny since sbcl-0.6.12.34 knows
940 (SUBTYPEP '(EQL 0) 'NUMBER) => T
943 (TIME (ROOM T)) reports more than 200 Mbytes consed even for
944 a clean, just-started SBCL system. And it seems to be right:
945 (ROOM T) can bring a small computer to its knees for a *long*
946 time trying to GC afterwards. Surely there's some more economical
947 way to implement (ROOM T).
950 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
952 ;;; This file fails to compile.
953 ;;; Maybe this bug is related to bugs #65, #70 in the BUGS file.
954 (in-package :cl-user)
960 ;; Uncomment and it works
963 In SBCL 0.6.12.42, the problem is
964 internal error, failed AVER:
965 "(COMMON-LISP:EQ (SB!C::LAMBDA-TAIL-SET SB!C::CALLER)
966 (SB!C::LAMBDA-TAIL-SET (SB!C::LAMBDA-HOME SB!C::CALLEE)))"
969 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
971 ;;; The compiler is flushing the argument type test, and the default
972 ;;; case in the cond, so that calling with say a fixnum 0 causes a
974 (declaim (optimize (safety 2) (speed 3)))
976 (declare (type (or string stream) x))
977 (cond ((typep x 'string) 'string)
978 ((typep x 'stream) 'stream)
981 The symptom in sbcl-0.6.12.42 on OpenBSD is actually (TST 0)=>STREAM
982 (not the SIGBUS reported in the comment) but that's broken too;
983 type declarations are supposed to be treated as assertions unless
984 SAFETY 0, so we should be getting a TYPE-ERROR.
987 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
989 (in-package :cl-user)
990 ;;; Produces an assertion failures when compiled.
992 (declare (type (or (function (t) t) null) z))
993 (let ((z (or z #'identity)))
994 (declare (type (function (t) t) z))
996 The error in sbcl-0.6.12.42 is
997 internal error, failed AVER:
998 "(COMMON-LISP:NOT (COMMON-LISP:EQ SB!C::CHECK COMMON-LISP:T))"
1001 reported by Martin Atzmueller 2001-06-25; taken from CMU CL bugs
1002 collection; apparently originally reported by Bruno Haible
1003 (in-package :cl-user)
1004 ;;; From: Bruno Haible
1005 ;;; Subject: scope of SPECIAL declarations
1006 ;;; It seems CMUCL has a bug relating to the scope of SPECIAL
1007 ;;; declarations. I observe this with "CMU Common Lisp 18a x86-linux
1010 (declare (special x))
1013 (declare (special x)) y)))
1014 ;;; Gives: 0 (this should return 1 according to CLHS)
1016 (declare (special x))
1019 (declare (special x)) y)))
1020 ;;; Gives: 1 (correct).
1021 The reported results match what we get from the interpreter
1025 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
1027 (in-package :cl-user)
1028 ;;; From: David Gadbois <gadbois@cyc.com>
1030 ;;; Logical pathnames aren't externalizable.
1032 (let ((tempfile "/tmp/test.lisp"))
1033 (setf (logical-pathname-translations "XXX")
1034 '(("XXX:**;*.*" "/tmp/**/*.*")))
1035 (with-open-file (out tempfile :direction :output)
1036 (write-string "(defvar *path* #P\"XXX:XXX;FOO.LISP\")" out))
1037 (compile-file tempfile))
1038 The error message in sbcl-0.6.12.42 is
1040 ; (while making load form for #<SB-IMPL::LOGICAL-HOST "XXX">)
1041 ; A logical host can't be dumped as a constant: #<SB-IMPL::LOGICAL-HOST "XXX">
1044 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
1046 (in-package :cl-user)
1047 ;;; This file causes the byte compiler to fail.
1048 (declaim (optimize (speed 0) (safety 1)))
1051 (multiple-value-list
1053 (return-from tst1)))))
1054 The error message in sbcl-0.6.12.42 is
1055 internal error, failed AVER:
1056 "(COMMON-LISP:EQUAL (SB!C::BYTE-BLOCK-INFO-START-STACK SB!INT:INFO) SB!C::STACK)"
1059 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
1061 (in-package :cl-user)
1062 ;;; The following invokes a compiler error.
1063 (declaim (optimize (speed 2) (debug 3)))
1066 (unwind-protect nil)))
1070 The error message in sbcl-0.6.12.42 is
1071 internal error, failed AVER:
1072 "(COMMON-LISP:EQ (SB!C::TN-ENVIRONMENT SB!C:TN) SB!C::TN-ENV)"
1075 When the compiler inline expands functions, it may be that different
1076 kinds of return values are generated from different code branches.
1077 E.g. an inline expansion of POSITION generates integer results
1078 from one branch, and NIL results from another. When that inline
1079 expansion is used in a context where only one of those results
1082 (aref *a1* (position x *a2*)))
1083 and the compiler can't prove that the unacceptable branch is
1084 never taken, then bogus type mismatch warnings can be generated.
1085 If you need to suppress the type mismatch warnings, you can
1086 suppress the inline expansion,
1088 #+sbcl (declare (notinline position)) ; to suppress bug 117 bogowarnings
1089 (aref *a1* (position x *a2*)))
1090 or, sometimes, suppress them by declaring the result to be of an
1093 (aref *a1* (the integer (position x *a2*))))
1095 This is not a new compiler problem in 0.7.0, but the new compiler
1096 transforms for FIND, POSITION, FIND-IF, and POSITION-IF make it
1097 more conspicuous. If you don't need performance from these functions,
1098 and the bogus warnings are a nuisance for you, you can return to
1099 your pre-0.7.0 state of grace with
1100 #+sbcl (declaim (notinline find position find-if position-if)) ; bug 117..
1103 as reported by Eric Marsden on cmucl-imp@cons.org 2001-08-14:
1104 (= (FLOAT 1 DOUBLE-FLOAT-EPSILON)
1105 (+ (FLOAT 1 DOUBLE-FLOAT-EPSILON) DOUBLE-FLOAT-EPSILON)) => T
1106 when of course it should be NIL. (He says it only fails for X86,
1107 not SPARC; dunno about Alpha.)
1109 Also, "the same problem exists for LONG-FLOAT-EPSILON,
1110 DOUBLE-FLOAT-NEGATIVE-EPSILON, LONG-FLOAT-NEGATIVE-EPSILON (though
1111 for the -negative- the + is replaced by a - in the test)."
1113 Raymond Toy comments that this is tricky on the X86 since its FPU
1114 uses 80-bit precision internally.
1117 a bug in the byte compiler and/or interpreter: Compile
1118 (IN-PACKAGE :CL-USER)
1119 (DECLAIM (OPTIMIZE (SPEED 0) (SAFETY 1) (DEBUG 1)))
1120 (DEFUN BAR (&REST DIMS)
1121 (IF (EVERY #'INTEGERP DIMS)
1124 then execute (BAR '(1 2 3 4)). In sbcl-0.pre7.14.flaky4.8
1125 this gives a TYPE-ERROR,
1126 The value #:UNINITIALIZED-EVAL-STACK-ELEMENT is not
1127 of type (MOD 536870911).
1128 The same error will probably occur in earlier versions as well,
1129 although the name of the uninitialized-element placeholder will
1132 The same thing happens if the compiler macro expansion of
1133 EVERY into MAP is hand-expanded:
1135 (if (block blockname
1138 (let ((pred-value (funcall #'integerp dim)))
1140 (return-from blockname
1146 CMU CL doesn't have this compiler macro expansion, so it was
1147 immune to the original bug in BAR, but once we hand-expand it
1148 into BAR2, CMU CL 18c has the same bug. (Run (BAR '(NIL NIL)).)
1150 The native compiler handles it fine, both in SBCL and in CMU CL.
1153 The compiler incorrectly figures the return type of
1154 (DEFUN FOO (FRAME UP-FRAME)
1161 This problem exists in CMU CL 18c too. When I reported it on
1162 cmucl-imp@cons.org, Raymond Toy replied 23 Aug 2001 with
1163 a partial explanation, but no fix has been found yet.
1166 Even in sbcl-0.pre7.x, which is supposed to be free of the old
1167 non-ANSI behavior of treating the function return type inferred
1168 from the current function definition as a declaration of the
1169 return type from any function of that name, the return type of NIL
1170 is attached to FOO in 120a above, and used to optimize code which
1174 There was some sort of screwup in handling of
1175 (IF (NOT (IGNORE-ERRORS ..))). E.g.
1177 (if (not (ignore-errors
1178 (make-pathname :host "foo" :directory "!bla" :name "bar")))
1180 (error "notunlessnot")))
1181 The (NOT (IGNORE-ERRORS ..)) form evaluates to T, so this should be
1182 printing "ok", but instead it's going to the ERROR. This problem
1183 seems to've been introduced by MNA's HANDLER-CASE patch (sbcl-devel
1184 2001-07-17) and as a workaround (put in sbcl-0.pre7.14.flaky4.12)
1185 I reverted back to the old weird HANDLER-CASE code. However, I
1186 think the problem looks like a compiler bug in handling RETURN-FROM,
1187 so I left the MNA-patched code in HANDLER-CASE (suppressed with
1188 #+NIL) and I'd like to go back to see whether this really is
1189 a compiler bug before I delete this BUGS entry.
1192 The *USE-IMPLEMENTATION-TYPES* hack causes bugs, particularly
1193 (IN-PACKAGE :SB-KERNEL)
1194 (TYPE= (SPECIFIER-TYPE '(VECTOR T))
1195 (SPECIFIER-TYPE '(VECTOR UNDEFTYPE)))
1196 Then because of this, the compiler bogusly optimizes
1197 (TYPEP #(11) '(SIMPLE-ARRAY UNDEF-TYPE 1))
1198 to T. Unfortunately, just setting *USE-IMPLEMENTATION-TYPES* to
1199 NIL around sbcl-0.pre7.14.flaky4.12 didn't work: the compiler complained
1200 about type mismatches (probably harmlessly, another instance of bug 117);
1201 and then cold init died with a segmentation fault.
1204 As of version 0.pre7.14, SBCL's implementation of MACROLET makes
1205 the entire lexical environment at the point of MACROLET available
1206 in the bodies of the macroexpander functions. In particular, it
1207 allows the function bodies (which run at compile time) to try to
1208 access lexical variables (which are only defined at runtime).
1209 It doesn't even issue a warning, which is bad.
1211 The SBCL behavior arguably conforms to the ANSI spec (since the
1212 spec says that the behavior is undefined, ergo anything conforms).
1213 However, it would be better to issue a compile-time error.
1214 Unfortunately I (WHN) don't see any simple way to detect this
1215 condition in order to issue such an error, so for the meantime
1216 SBCL just does this weird broken "conforming" thing.
1218 The ANSI standard says, in the definition of the special operator
1220 The macro-expansion functions defined by MACROLET are defined
1221 in the lexical environment in which the MACROLET form appears.
1222 Declarations and MACROLET and SYMBOL-MACROLET definitions affect
1223 the local macro definitions in a MACROLET, but the consequences
1224 are undefined if the local macro definitions reference any
1225 local variable or function bindings that are visible in that
1226 lexical environment.
1227 Then it seems to contradict itself by giving the example
1229 (macrolet ((fudge (z)
1230 ;The parameters x and flag are not accessible
1231 ; at this point; a reference to flag would be to
1232 ; the global variable of that name.
1233 ` (if flag (* ,z ,z) ,z)))
1234 ;The parameters x and flag are accessible here.
1238 The comment "a reference to flag would be to the global variable
1239 of the same name" sounds like good behavior for the system to have.
1240 but actual specification quoted above says that the actual behavior
1243 KNOWN BUGS RELATED TO THE IR1 INTERPRETER
1245 (Note: At some point, the pure interpreter (actually a semi-pure
1246 interpreter aka "the IR1 interpreter") will probably go away, replaced
1248 (DEFUN EVAL (X) (FUNCALL (COMPILE NIL (LAMBDA ..)))))
1249 and at that time these bugs should either go away automatically or
1250 become more tractable to fix. Until then, they'll probably remain,
1251 since some of them aren't considered urgent, and the rest are too hard
1252 to fix as long as so many special cases remain. After the IR1
1253 interpreter goes away is also the preferred time to start
1254 systematically exterminating cases where debugging functionality
1255 (backtrace, breakpoint, etc.) breaks down, since getting rid of the
1256 IR1 interpreter will reduce the number of special cases we need to
1260 The FUNCTION special operator doesn't check properly whether its
1261 argument is a function name. E.g. (FUNCTION (X Y)) returns a value
1262 instead of failing with an error. (Later attempting to funcall the
1263 value does cause an error.)
1266 COMPILED-FUNCTION-P bogusly reports T for interpreted functions:
1267 * (DEFUN FOO (X) (- 12 X))
1269 * (COMPILED-FUNCTION-P #'FOO)
1274 (DEFVAR *SUPPRESS-P* T)
1275 (EVAL '(UNLESS *SUPPRESS-P*
1276 (EVAL-WHEN (:COMPILE-TOPLEVEL :LOAD-TOPLEVEL :EXECUTE)
1277 (FORMAT T "surprise!"))))
1278 prints "surprise!". Probably the entire EVAL-WHEN mechanism ought to be
1279 rewritten from scratch to conform to the ANSI definition, abandoning
1280 the *ALREADY-EVALED-THIS* hack which is used in sbcl-0.6.8.9 (and
1281 in the original CMU CL source, too). This should be easier to do --
1282 though still nontrivial -- once the various IR1 interpreter special
1286 EVAL-WHEN's idea of what's a toplevel form is even more screwed up
1287 than the example in IR1-3 would suggest, since COMPILE-FILE and
1288 COMPILE both print both "right now!" messages when compiling the
1292 (EVAL-WHEN (:COMPILE-TOPLEVEL :LOAD-TOPLEVEL :EXECUTE)
1293 (PRINT "yes! right now!"))
1296 (EVAL-WHEN (:COMPILE-TOPLEVEL :LOAD-TOPLEVEL :EXECUTE)
1297 (PRINT "no! right now!"))
1299 and while EVAL doesn't print the "right now!" messages, the first
1300 FUNCALL on the value returned by EVAL causes both of them to be printed.
1303 The system accepts DECLAIM in most places where DECLARE would be
1304 accepted, without even issuing a warning. ANSI allows this, but since
1305 it's fairly easy to mistype DECLAIM instead of DECLARE, and the
1306 meaning is rather different, and it's unlikely that the user
1307 has a good reason for doing DECLAIM not at top level, it would be
1308 good to issue a STYLE-WARNING when this happens. A possible
1309 fix would be to issue STYLE-WARNINGs for DECLAIMs not at top level,
1310 or perhaps to issue STYLE-WARNINGs for any EVAL-WHEN not at top level.
1311 [This is considered an IR1-interpreter-related bug because until
1312 EVAL-WHEN is rewritten, which won't happen until after the IR1
1313 interpreter is gone, the system's notion of what's a top-level form
1314 and what's not will remain too confused to fix this problem.]
1317 (another wishlist thing..) Reimplement DEFMACRO to be basically
1318 like DEFMACRO-MUNDANELY, just using EVAL-WHEN.