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 b: a messy one involving package iteration:
393 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<))))
394 Should be: (("blah" "blah2") ("blah2"))
395 SBCL: (("blah") ("blah2"))
396 * (LET ((X 1)) (LOOP FOR I BY (INCF X) FROM X TO 10 COLLECT I))
397 doesn't work -- SBCL's LOOP says BY isn't allowed in a FOR clause.
400 type system errors reported by Peter Van Eynde July 25, 2000:
401 a: (SUBTYPEP 'BIGNUM 'INTEGER) => NIL, NIL
402 but should be (VALUES T T) instead.
403 b: (SUBTYPEP 'EXTENDED-CHAR 'CHARACTER) => NIL, NIL
404 but should be (VALUES T T) instead.
405 c: (SUBTYPEP '(INTEGER (0) (0)) 'NIL) dies with nested errors.
406 d: In general, the system doesn't like '(INTEGER (0) (0)) -- it
407 blows up at the level of SPECIFIER-TYPE with
408 "Lower bound (0) is greater than upper bound (0)." Probably
409 SPECIFIER-TYPE should return NIL instead.
410 e: (TYPEP 0 '(COMPLEX (EQL 0)) fails with
411 "Component type for Complex is not numeric: (EQL 0)."
412 This might be easy to fix; the type system already knows
413 that (SUBTYPEP '(EQL 0) 'NUMBER) is true.
414 f: The type system doesn't know about the condition system,
415 so that e.g. (TYPEP 'SIMPLE-ERROR 'ERROR)=>NIL.
416 g: The type system isn't all that smart about relationships
417 between hairy types, as shown in the type.erg test results,
418 e.g. (SUBTYPEP 'CONS '(NOT ATOM)) => NIL, NIL.
421 miscellaneous errors reported by Peter Van Eynde July 25, 2000:
423 (DEFGENERIC FOO02 (X))
424 (DEFMETHOD FOO02 ((X NUMBER)) T)
425 (LET ((M (FIND-METHOD (FUNCTION FOO02)
427 (LIST (FIND-CLASS (QUOTE NUMBER))))))
428 (REMOVE-METHOD (FUNCTION FOO02) M)
429 (DEFGENERIC FOO03 (X))
430 (ADD-METHOD (FUNCTION FOO03) M)))
431 should give an error, but SBCL allows it.
432 b: READ should probably return READER-ERROR, not the bare
433 arithmetic error, when input a la "1/0" or "1e1000" causes
437 It has been reported (e.g. by Peter Van Eynde) that there are
438 several metaobject protocol "errors". (In order to fix them, we might
439 need to document exactly what metaobject protocol specification
440 we're following -- the current code is just inherited from PCL.)
443 another error from Peter Van Eynde 5 September 2000:
444 (FORMAT NIL "~F" "FOO") should work, but instead reports an error.
445 PVE submitted a patch to deal with this bug, but it exposes other
446 comparably serious bugs, so I didn't apply it. It looks as though
447 the FORMAT code needs a fair amount of rewriting in order to comply
448 with the various details of the ANSI spec.
451 The implementation of #'+ returns its single argument without
452 type checking, e.g. (+ "illegal") => "illegal".
455 Attempting to use COMPILE on something defined by DEFMACRO fails:
456 (DEFMACRO FOO (X) (CONS X X))
458 Error in function C::GET-LAMBDA-TO-COMPILE:
459 #<Closure Over Function "DEFUN (SETF MACRO-FUNCTION)" {480E21B1}> was defined in a non-null environment.
462 (SUBTYPEP '(AND ZILCH INTEGER) 'ZILCH) => NIL, NIL
463 Note: I looked into fixing this in 0.6.11.15, but gave up. The
464 problem seems to be that there are two relevant type methods for
465 the subtypep operation, HAIRY :COMPLEX-SUBTYPEP-ARG2 and
466 INTERSECTION :COMPLEX-SUBTYPEP-ARG1, and only the first is
467 called. This could be fixed, but type dispatch is messy and
468 confusing enough already, I don't want to complicate it further.
469 Perhaps someday we can make CLOS cross-compiled (instead of compiled
470 after bootstrapping) so that we don't need to have the type system
471 available before CLOS, and then we can rewrite the type methods to
472 CLOS methods, and then expressing the solutions to stuff like this
473 should become much more straightforward. -- WHN 2001-03-14
476 The debugger LIST-LOCATIONS command doesn't work properly.
479 Compiling and loading
480 (DEFUN FAIL (X) (THROW 'FAIL-TAG X))
482 then requesting a BACKTRACE at the debugger prompt gives no information
483 about where in the user program the problem occurred.
486 The compiler is supposed to do type inference well enough that
489 ((SIMPLE-ARRAY SINGLE-FLOAT)
491 (DECLARE (TYPE (SIMPLE-ARRAY SINGLE-FLOAT) X))
494 is redundant. However, as reported by Juan Jose Garcia Ripoll for
495 CMU CL, it sometimes doesn't. Adding declarations is a pretty good
496 workaround for the problem for now, but can't be done by the TYPECASE
497 macros themselves, since it's too hard for the macro to detect
498 assignments to the variable within the clause.
499 Note: The compiler *is* smart enough to do the type inference in
500 many cases. This case, derived from a couple of MACROEXPAND-1
501 calls on Ripoll's original test case,
503 (DECLARE (OPTIMIZE SPEED (SAFETY 0)))
504 (COND ((TYPEP A '(SIMPLE-ARRAY SINGLE-FLOAT)) NIL
505 (LET ((LENGTH (ARRAY-TOTAL-SIZE A)))
506 (LET ((I 0) (G2554 LENGTH))
507 (DECLARE (TYPE REAL G2554) (TYPE REAL I))
510 (WHEN (>= I G2554) (GO SB-LOOP::END-LOOP))
511 (SETF (ROW-MAJOR-AREF A I) (- (ROW-MAJOR-AREF A I)))
512 (GO SB-LOOP::NEXT-LOOP)
513 SB-LOOP::END-LOOP))))))
514 demonstrates the problem; but the problem goes away if the TAGBODY
515 and GO forms are removed (leaving the SETF in ordinary, non-looping
516 code), or if the TAGBODY and GO forms are retained, but the
517 assigned value becomes 0.0 instead of (- (ROW-MAJOR-AREF A I)).
520 Paul Werkowski wrote on cmucl-imp@cons.org 2000-11-15
521 I am looking into this problem that showed up on the cmucl-help
522 list. It seems to me that the "implementation specific environment
523 hacking functions" found in pcl/walker.lisp are completely messed
524 up. The good thing is that they appear to be barely used within
525 PCL and the munged environment object is passed to cmucl only
526 in calls to macroexpand-1, which is probably why this case fails.
527 SBCL uses essentially the same code, so if the environment hacking
528 is screwed up, it affects us too.
531 Using the pretty-printer from the command prompt gives funny
532 results, apparently because the pretty-printer doesn't know
533 about user's command input, including the user's carriage return
534 that the user, and therefore the pretty-printer thinks that
535 the new output block should start indented 2 or more characters
536 rightward of the correct location.
539 (probably related to bug #70; maybe related to bug #109)
540 As reported by Carl Witty on submit@bugs.debian.org 1999-05-08,
542 (in-package "CL-USER")
543 (defun equal-terms (termx termy)
545 ((alpha-equal-bound-term-lists (listx listy)
546 (or (and (null listx) (null listy))
548 (let ((bindings-x (bindings-of-bound-term (car listx)))
549 (bindings-y (bindings-of-bound-term (car listy))))
550 (if (and (null bindings-x) (null bindings-y))
551 (alpha-equal-terms (term-of-bound-term (car listx))
552 (term-of-bound-term (car listy)))
553 (and (= (length bindings-x) (length bindings-y))
555 (enter-binding-pairs (bindings-of-bound-term (car listx))
556 (bindings-of-bound-term (car listy)))
557 (alpha-equal-terms (term-of-bound-term (car listx))
558 (term-of-bound-term (car listy)))
559 (exit-binding-pairs (bindings-of-bound-term (car listx))
560 (bindings-of-bound-term (car listy)))))))
561 (alpha-equal-bound-term-lists (cdr listx) (cdr listy)))))
563 (alpha-equal-terms (termx termy)
564 (if (and (variable-p termx)
566 (equal-bindings (id-of-variable-term termx)
567 (id-of-variable-term termy))
568 (and (equal-operators-p (operator-of-term termx) (operator-of-term termy))
569 (alpha-equal-bound-term-lists (bound-terms-of-term termx)
570 (bound-terms-of-term termy))))))
574 (with-variable-invocation (alpha-equal-terms termx termy))))))
575 causes an assertion failure
576 The assertion (EQ (C::LAMBDA-TAIL-SET C::CALLER)
577 (C::LAMBDA-TAIL-SET (C::LAMBDA-HOME C::CALLEE))) failed.
579 Bob Rogers reports (1999-07-28 on cmucl-imp@cons.org) a smaller test
580 case with the same problem:
581 (defun parse-fssp-alignment ()
582 ;; Given an FSSP alignment file named by the argument . . .
583 (labels ((get-fssp-char ()
587 ;; Stub body, enough to tickle the bug.
588 (list (read-fssp-char)
592 ANSI specifies that the RESULT-TYPE argument of CONCATENATE must be
593 a subtype of SEQUENCE, but CONCATENATE doesn't check this properly:
594 (CONCATENATE 'SIMPLE-ARRAY #(1 2) '(3)) => #(1 2 3)
595 This also leads to funny behavior when derived type specifiers
596 are used, as originally reported by Milan Zamazal for CMU CL (on the
597 Debian bugs mailing list (?) 2000-02-27), then reported by Martin
598 Atzmueller for SBCL (2000-10-01 on sbcl-devel@lists.sourceforge.net):
599 (DEFTYPE FOO () 'SIMPLE-ARRAY)
600 (CONCATENATE 'FOO #(1 2) '(3))
601 => #<ARRAY-TYPE SIMPLE-ARRAY> is a bad type specifier for
603 The derived type specifier FOO should act the same way as the
604 built-in type SIMPLE-ARRAY here, but it doesn't. That problem
605 doesn't seem to exist for sequence types:
606 (DEFTYPE BAR () 'SIMPLE-VECTOR)
607 (CONCATENATE 'BAR #(1 2) '(3)) => #(1 2 3)
610 As reported by Winton Davies on a CMU CL mailing list 2000-01-10,
611 and reported for SBCL by Martin Atzmueller 2000-10-20: (TRACE GETHASH)
612 crashes SBCL. In general tracing anything which is used in the
613 implementation of TRACE is likely to have the same problem.
616 As reported by Daniel Solaz on cmucl-help@cons.org 2000-11-23,
617 SXHASH returns the same value for all non-STRUCTURE-OBJECT instances,
618 notably including all PCL instances. There's a limit to how much
619 SXHASH can do to return unique values for instances, but at least
620 it should probably look at the class name, the way that it does
621 for STRUCTURE-OBJECTs.
624 As reported by Martin Atzmueller on the sbcl-devel list 2000-11-22,
625 > There remains one issue, that is a bug in SBCL:
626 > According to my interpretation of the spec, the ":" and "@" modifiers
627 > should appear _after_ the comma-seperated arguments.
628 > Well, SBCL (and CMUCL for that matter) accept
629 > (ASSERT (STRING= (FORMAT NIL "~:8D" 1) " 1"))
630 > where the correct way (IMHO) should be
631 > (ASSERT (STRING= (FORMAT NIL "~8:D" 1) " 1"))
632 Probably SBCL should stop accepting the "~:8D"-style format arguments,
633 or at least issue a warning.
636 (probably related to bug #65; maybe related to bug #109)
637 The compiler doesn't like &OPTIONAL arguments in LABELS and FLET
639 (DEFUN FIND-BEFORE (ITEM SEQUENCE &KEY (TEST #'EQL))
640 (LABELS ((FIND-ITEM (OBJ SEQ TEST &OPTIONAL (VAL NIL))
641 (LET ((ITEM (FIRST SEQ)))
644 ((FUNCALL TEST OBJ ITEM)
647 (FIND-ITEM OBJ (REST SEQ) TEST (NCONC VAL `(,ITEM))))))))
648 (FIND-ITEM ITEM SEQUENCE TEST)))
649 from David Young's bug report on cmucl-help@cons.org 30 Nov 2000
650 causes sbcl-0.6.9 to fail with
651 error in function SB-KERNEL:ASSERT-ERROR:
652 The assertion (EQ (SB-C::LAMBDA-TAIL-SET SB-C::CALLER)
653 (SB-C::LAMBDA-TAIL-SET
654 (SB-C::LAMBDA-HOME SB-C::CALLEE))) failed.
657 (DECLAIM (OPTIMIZE ..)) doesn't work. E.g. even after
658 (DECLAIM (OPTIMIZE (SPEED 3))), things are still optimized with
659 the previous SPEED policy. This bug will probably get fixed in
660 0.6.9.x in a general cleanup of optimization policy.
663 (DECLAIM (OPTIMIZE ..)) doesn't work properly inside LOCALLY forms.
666 As noted in the ANSI specification for COERCE, (COERCE 3 'COMPLEX)
667 gives a result which isn't COMPLEX. The result type optimizer
668 for COERCE doesn't know this, perhaps because it was written before
669 ANSI threw this curveball: the optimizer thinks that COERCE always
670 returns a result of the specified type. Thus while the interpreted
672 (DEFUN TRICKY (X) (TYPEP (COERCE X 'COMPLEX) 'COMPLEX))
673 returns the correct result,
675 the compiled function
681 As reported by Martin Atzmueller on sbcl-devel 26 Dec 2000,
682 ANSI says that WITH-OUTPUT-TO-STRING should have a keyword
683 :ELEMENT-TYPE, but in sbcl-0.6.9 this is not defined for
684 WITH-OUTPUT-TO-STRING.
687 ANSI says in one place that type declarations can be abbreviated even
688 when the type name is not a symbol, e.g.
689 (DECLAIM ((VECTOR T) *FOOVECTOR*))
690 SBCL doesn't support this. But ANSI says in another place that this
691 isn't allowed. So it's not clear this is a bug after all. (See the
692 e-mail on cmucl-help@cons.org on 2001-01-16 and 2001-01-17 from WHN
696 as pointed out by Dan Barlow on sbcl-devel 2000-07-02:
697 The PICK-TEMPORARY-FILE-NAME utility used by LOAD-FOREIGN uses
698 an easily guessable temporary filename in a way which might open
699 applications using LOAD-FOREIGN to hijacking by malicious users
700 on the same machine. Incantations for doing this safely are
701 floating around the net in various "how to write secure programs
702 despite Unix" documents, and it would be good to (1) fix this in
703 LOAD-FOREIGN, and (2) hunt for any other code which uses temporary
704 files and make it share the same new safe logic.
707 (fixed early Feb 2001 by MNA)
710 As reported by wbuss@TELDA.NET (Wolfhard Buss) on cmucl-help
713 (loop with (a . b) of-type float = '(0.0 . 1.0)
714 and (c . d) of-type float = '(2.0 . 3.0)
715 return (list a b c d))
716 should evaluate to (0.0 1.0 2.0 3.0). cmucl-18c disagrees and
717 invokes the debugger: "B is not of type list".
718 SBCL does the same thing.
721 Functions are assigned names based on the context in which they're
722 defined. This is less than ideal for the functions which are
723 used to implement CLOS methods. E.g. the output of
724 (DESCRIBE 'PRINT-OBJECT) lists functions like
725 #<FUNCTION "DEF!STRUCT (TRACE-INFO (:MAKE-LOAD-FORM-FUN SB-KERNEL:JUST-DUMP-IT-NORMALLY) (:PRINT-OBJECT #))" {1020E49}>
727 #<FUNCTION "MACROLET ((FORCE-DELAYED-DEF!METHODS NIL #))" {1242871}>
728 It would be better if these functions' names always identified
729 them as methods, and identified their generic functions and
733 RANDOM-INTEGER-EXTRA-BITS=10 may not be large enough for the RANDOM
734 RNG to be high quality near RANDOM-FIXNUM-MAX; it looks as though
735 the mean of the distribution can be systematically O(0.1%) wrong.
736 Just increasing R-I-E-B is probably not a good solution, since
737 it would decrease efficiency more than is probably necessary. Perhaps
738 using some sort of accept/reject method would be better.
741 (SUBTYPEP '(SATISFIES SOME-UNDEFINED-FUN) NIL)=>NIL,T (should be NIL,NIL)
744 Internally the compiler sometimes evaluates
745 (sb-kernel:type/= (specifier-type '*) (specifier-type t))
746 (I stumbled across this when I added an
747 (assert (not (eq type1 *wild-type*)))
748 in the NAMED :SIMPLE-= type method.) '* isn't really a type, and
749 in a type context should probably be translated to T, and so it's
750 probably to ask whether it's equal to the T type and then (using the
751 EQ type comparison in the NAMED :SIMPLE-= type method) return NIL.
752 (I haven't tried to investigate this bug enough to guess whether
753 there might be any user-level symptoms.)
756 a latent cross-compilation/bootstrapping bug: The cross-compilation
757 host's CL:CHAR-CODE-LIMIT is used in target code in readtable.lisp
758 and possibly elsewhere. Instead, we should use the target system's
759 CHAR-CODE-LIMIT. This will probably cause problems if we try to
760 bootstrap on a system which uses a different value of CHAR-CODE-LIMIT
764 (subtypep '(or (integer -1 1)
768 (integer -1 1))) => NIL,T
769 An analogous problem with SINGLE-FLOAT and REAL types was fixed in
770 sbcl-0.6.11.22, but some peculiarites of the RATIO type make it
771 awkward to generalize the fix to INTEGER and RATIONAL. It's not
772 clear what's the best fix. (See the "bug in type handling" discussion
773 on cmucl-imp ca. 2001-03-22 and ca. 2001-02-12.)
776 In sbcl-0.6.11.26, (COMPILE 'IN-HOST-COMPILATION-MODE) in
777 src/cold/shared.lisp doesn't correctly translate the
779 (defun in-host-compilation-mode (fn)
780 (let ((*features* (cons :sb-xc-host *features*))
781 ;; the CROSS-FLOAT-INFINITY-KLUDGE, as documented in
782 ;; base-target-features.lisp-expr:
783 (*shebang-features* (set-difference *shebang-features*
784 '(:sb-propagate-float-type
785 :sb-propagate-fun-type))))
786 (with-additional-nickname ("SB-XC" "SB!XC")
788 No error is reported by the compiler, but when the function is executed,
790 TYPE-ERROR in SB-KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:
791 (:LINUX :X86 :IEEE-FLOATING-POINT :SB-CONSTRAIN-FLOAT-TYPE :SB-TEST
792 :SB-INTERPRETER :SB-DOC :UNIX ...) is not of type SYMBOL.
795 Inconsistencies between derived and declared VALUES return types for
796 DEFUN aren't checked very well. E.g. the logic which successfully
797 catches problems like
798 (declaim (ftype (function (fixnum) float) foo))
800 (declare (type integer x))
801 (values x)) ; wrong return type, detected, gives warning, good!
803 (declaim (ftype (function (t) (values t t)) bar))
805 (values x)) ; wrong number of return values, no warning, bad!
806 The cause of this is seems to be that (1) the internal function
807 VALUES-TYPES-EQUAL-OR-INTERSECT used to make the check handles its
808 arguments symmetrically, and (2) when the type checking code was
809 written back when when SBCL's code was still CMU CL, the intent
811 (declaim (ftype (function (t) t) bar))
813 (values x x)) ; wrong number of return values; should give warning?
814 not be warned for, because a two-valued return value is considered
815 to be compatible with callers who expects a single value to be
816 returned. That intent is probably not appropriate for modern ANSI
817 Common Lisp, but fixing this might be complicated because of other
818 divergences between auld-style and new-style handling of
819 multiple-VALUES types. (Some issues related to this were discussed
820 on cmucl-imp at some length sometime in 2000.)
823 The facility for dumping a running Lisp image to disk gets confused
824 when run without the PURIFY option, and creates an unnecessarily large
825 core file (apparently representing memory usage up to the previous
826 high-water mark). Moreover, when the file is loaded, it confuses the
827 GC, so that thereafter memory usage can never be reduced below that
831 The TRACE facility can't be used on some kinds of functions.
832 (Basically, the breakpoint facility was incompletely implemented
833 in the X86 port of CMU CL, and hasn't been fixed in SBCL.)
836 In sbcl-0.6.11.41 (and in all earlier SBCL, and in CMU
837 CL), out-of-line structure slot setters are horribly inefficient
838 whenever the type of the slot is declared, because out-of-line
839 structure slot setters are implemented as closures to save space,
840 so the compiler doesn't compile the type test into code, but
841 instead just saves the type in a lexical closure and interprets it
843 A proper solution involves deciding whether it's really worth
844 saving space by implementing structure slot accessors as closures.
845 (If it's not worth it, the problem vanishes automatically. If it
846 is worth it, there are hacks we could use to force type tests to
847 be compiled anyway, and even shared. E.g. we could implement
848 an EQUAL hash table mapping from types to compiled type tests,
849 and save the appropriate compiled type test as part of each lexical
850 closure; or we could make the lexical closures be placeholders
851 which overwrite their old definition as a lexical closure with
852 a new compiled definition the first time that they're called.)
853 As a workaround for the problem, #'(SETF FOO) expressions can
854 be replaced with (EFFICIENT-SETF-FUNCTION FOO), where
855 (defmacro efficient-setf-function (place-function-name)
856 (or #+sbcl (and (sb-impl::info :function :accessor-for place-function-name)
857 ;; a workaround for the problem, encouraging the
858 ;; inline expansion of the structure accessor, so
859 ;; that the compiler can optimize its type test
860 (let ((new-value (gensym "NEW-VALUE-"))
861 (structure-value (gensym "STRUCTURE-VALUE-")))
862 `(lambda (,new-value ,structure-value)
863 (setf (,place-function-name ,structure-value)
865 ;; no problem, can just use the ordinary expansion
866 `(function (setf ,place-function-name))))
869 DESCRIBE interacts poorly with *PRINT-CIRCLE*, e.g. the output from
870 (let ((*print-circle* t)) (describe (make-hash-table)))
872 #<HASH-TABLE :TEST EQL :COUNT 0 {90BBFC5}> is an . (EQL)
874 Its REHASH-SIZE is 1.5. Its REHASH-THRESHOLD is . (1.0)
875 It holds 0 key/value pairs.
876 where the ". (EQL)" and ". (1.0)" substrings are screwups.
877 (This is likely a pretty-printer problem which happens to
878 be exercised by DESCRIBE, not actually a DESCRIBE problem.)
881 There's apparently a bug in CEILING optimization which caused
882 Douglas Crosher to patch the CMU CL version. Martin Atzmueller
883 applied the patches to SBCL and they didn't seem to cause problems
884 (as reported sbcl-devel 2001-05-04). However, since the patches
885 modify nontrivial code which was apparently written incorrectly
886 the first time around, until regression tests are written I'm not
887 comfortable merging the patches in the CVS version of SBCL.
890 The error message for calls to structure accessors with the
891 wrong number of arguments is confusing and of the wrong
892 condition class (TYPE-ERROR instead of PROGRAM-ERROR):
893 * (defstruct foo x y)
895 debugger invoked on condition of type SIMPLE-TYPE-ERROR:
896 Structure for accessor FOO-X is not a FOO:
900 As reported by Arthur Lemmens sbcl-devel 2001-05-05, ANSI
901 requires that SYMBOL-MACROLET refuse to rebind special variables,
902 but SBCL doesn't do this. (Also as reported by AL in the same
903 message, SBCL depended on this nonconforming behavior to build
904 itself, because of the way that **CURRENT-SEGMENT** was implemented.
905 As of sbcl-0.6.12.x, this dependence on the nonconforming behavior
906 has been fixed, but the nonconforming behavior remains.)
909 As reported by Arthur Lemmens sbcl-devel 2001-05-05, ANSI's
910 definition of (LOOP .. DO ..) requires that the terms following
911 DO all be compound forms. SBCL's implementation of LOOP allows
912 non-compound forms (like the bare symbol COUNT, in his example)
916 (DESCRIBE 'SB-ALIEN:DEF-ALIEN-TYPE) reports the macro argument list
920 in #<PACKAGE "SB-ALIEN">.
921 Macro-function: #<FUNCTION "DEF!MACRO DEF-ALIEN-TYPE" {19F4A39}>
922 Macro arguments: (#:whole-470 #:environment-471)
923 On Sat, May 26, 2001 09:45:57 AM CDT it was compiled from:
924 /usr/stuff/sbcl/src/code/host-alieneval.lisp
925 Created: Monday, March 12, 2001 07:47:43 AM CST
928 (DESCRIBE 'STREAM-READ-BYTE)
931 (reported by Eric Marsden on cmucl-imp 2001-06-15)
933 (TYPEP 0 '(COMPLEX (EQL 0)))
934 signals an error in sbcl-0.6.12.34,
935 The component type for COMPLEX is not numeric: (EQL 0)
936 This is funny since sbcl-0.6.12.34 knows
937 (SUBTYPEP '(EQL 0) 'NUMBER) => T
940 (TIME (ROOM T)) reports more than 200 Mbytes consed even for
941 a clean, just-started SBCL system. And it seems to be right:
942 (ROOM T) can bring a small computer to its knees for a *long*
943 time trying to GC afterwards. Surely there's some more economical
944 way to implement (ROOM T).
947 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
949 ;;; This file fails to compile.
950 ;;; Maybe this bug is related to bugs #65, #70 in the BUGS file.
951 (in-package :cl-user)
957 ;; Uncomment and it works
960 In SBCL 0.6.12.42, the problem is
961 internal error, failed AVER:
962 "(COMMON-LISP:EQ (SB!C::LAMBDA-TAIL-SET SB!C::CALLER)
963 (SB!C::LAMBDA-TAIL-SET (SB!C::LAMBDA-HOME SB!C::CALLEE)))"
966 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
968 ;;; The compiler is flushing the argument type test, and the default
969 ;;; case in the cond, so that calling with say a fixnum 0 causes a
971 (declaim (optimize (safety 2) (speed 3)))
973 (declare (type (or string stream) x))
974 (cond ((typep x 'string) 'string)
975 ((typep x 'stream) 'stream)
978 The symptom in sbcl-0.6.12.42 on OpenBSD is actually (TST 0)=>STREAM
979 (not the SIGBUS reported in the comment) but that's broken too;
980 type declarations are supposed to be treated as assertions unless
981 SAFETY 0, so we should be getting a TYPE-ERROR.
984 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
986 (in-package :cl-user)
987 ;;; Produces an assertion failures when compiled.
989 (declare (type (or (function (t) t) null) z))
990 (let ((z (or z #'identity)))
991 (declare (type (function (t) t) z))
993 The error in sbcl-0.6.12.42 is
994 internal error, failed AVER:
995 "(COMMON-LISP:NOT (COMMON-LISP:EQ SB!C::CHECK COMMON-LISP:T))"
998 reported by Martin Atzmueller 2001-06-25; taken from CMU CL bugs
999 collection; apparently originally reported by Bruno Haible
1000 (in-package :cl-user)
1001 ;;; From: Bruno Haible
1002 ;;; Subject: scope of SPECIAL declarations
1003 ;;; It seems CMUCL has a bug relating to the scope of SPECIAL
1004 ;;; declarations. I observe this with "CMU Common Lisp 18a x86-linux
1007 (declare (special x))
1010 (declare (special x)) y)))
1011 ;;; Gives: 0 (this should return 1 according to CLHS)
1013 (declare (special x))
1016 (declare (special x)) y)))
1017 ;;; Gives: 1 (correct).
1018 The reported results match what we get from the interpreter
1022 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
1024 (in-package :cl-user)
1025 ;;; From: David Gadbois <gadbois@cyc.com>
1027 ;;; Logical pathnames aren't externalizable.
1029 (let ((tempfile "/tmp/test.lisp"))
1030 (setf (logical-pathname-translations "XXX")
1031 '(("XXX:**;*.*" "/tmp/**/*.*")))
1032 (with-open-file (out tempfile :direction :output)
1033 (write-string "(defvar *path* #P\"XXX:XXX;FOO.LISP\")" out))
1034 (compile-file tempfile))
1035 The error message in sbcl-0.6.12.42 is
1037 ; (while making load form for #<SB-IMPL::LOGICAL-HOST "XXX">)
1038 ; A logical host can't be dumped as a constant: #<SB-IMPL::LOGICAL-HOST "XXX">
1041 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
1043 (in-package :cl-user)
1044 ;;; This file causes the byte compiler to fail.
1045 (declaim (optimize (speed 0) (safety 1)))
1048 (multiple-value-list
1050 (return-from tst1)))))
1051 The error message in sbcl-0.6.12.42 is
1052 internal error, failed AVER:
1053 "(COMMON-LISP:EQUAL (SB!C::BYTE-BLOCK-INFO-START-STACK SB!INT:INFO) SB!C::STACK)"
1056 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
1058 (in-package :cl-user)
1059 ;;; The following invokes a compiler error.
1060 (declaim (optimize (speed 2) (debug 3)))
1063 (unwind-protect nil)))
1067 The error message in sbcl-0.6.12.42 is
1068 internal error, failed AVER:
1069 "(COMMON-LISP:EQ (SB!C::TN-ENVIRONMENT SB!C:TN) SB!C::TN-ENV)"
1072 When the compiler inline expands functions, it may be that different
1073 kinds of return values are generated from different code branches.
1074 E.g. an inline expansion of POSITION generates integer results
1075 from one branch, and NIL results from another. When that inline
1076 expansion is used in a context where only one of those results
1079 (aref *a1* (position x *a2*)))
1080 and the compiler can't prove that the unacceptable branch is
1081 never taken, then bogus type mismatch warnings can be generated.
1082 If you need to suppress the type mismatch warnings, you can
1083 suppress the inline expansion,
1085 #+sbcl (declare (notinline position)) ; to suppress bug 117 bogowarnings
1086 (aref *a1* (position x *a2*)))
1087 or, sometimes, suppress them by declaring the result to be of an
1090 (aref *a1* (the integer (position x *a2*))))
1092 This is not a new compiler problem in 0.7.0, but the new compiler
1093 transforms for FIND, POSITION, FIND-IF, and POSITION-IF make it
1094 more conspicuous. If you don't need performance from these functions,
1095 and the bogus warnings are a nuisance for you, you can return to
1096 your pre-0.7.0 state of grace with
1097 #+sbcl (declaim (notinline find position find-if position-if)) ; bug 117..
1100 as reported by Eric Marsden on cmucl-imp@cons.org 2001-08-14:
1101 (= (FLOAT 1 DOUBLE-FLOAT-EPSILON)
1102 (+ (FLOAT 1 DOUBLE-FLOAT-EPSILON) DOUBLE-FLOAT-EPSILON)) => T
1103 when of course it should be NIL. (He says it only fails for X86,
1104 not SPARC; dunno about Alpha.)
1106 Also, "the same problem exists for LONG-FLOAT-EPSILON,
1107 DOUBLE-FLOAT-NEGATIVE-EPSILON, LONG-FLOAT-NEGATIVE-EPSILON (though
1108 for the -negative- the + is replaced by a - in the test)."
1110 Raymond Toy comments that this is tricky on the X86 since its FPU
1111 uses 80-bit precision internally.
1114 a bug in the byte compiler and/or interpreter: Compile
1115 (IN-PACKAGE :CL-USER)
1116 (DECLAIM (OPTIMIZE (SPEED 0) (SAFETY 1) (DEBUG 1)))
1117 (DEFUN BAR (&REST DIMS)
1118 (IF (EVERY #'INTEGERP DIMS)
1121 then execute (BAR '(1 2 3 4)). In sbcl-0.pre7.14.flaky4.8
1122 this gives a TYPE-ERROR,
1123 The value #:UNINITIALIZED-EVAL-STACK-ELEMENT is not
1124 of type (MOD 536870911).
1125 The same error will probably occur in earlier versions as well,
1126 although the name of the uninitialized-element placeholder will
1129 The same thing happens if the compiler macro expansion of
1130 EVERY into MAP is hand-expanded:
1132 (if (block blockname
1135 (let ((pred-value (funcall #'integerp dim)))
1137 (return-from blockname
1143 CMU CL doesn't have this compiler macro expansion, so it was
1144 immune to the original bug in BAR, but once we hand-expand it
1145 into BAR2, CMU CL 18c has the same bug. (Run (BAR '(NIL NIL)).)
1147 The native compiler handles it fine, both in SBCL and in CMU CL.
1150 The compiler incorrectly figures the return type of
1151 (DEFUN FOO (FRAME UP-FRAME)
1158 This problem exists in CMU CL 18c too. When I reported it on
1159 cmucl-imp@cons.org, Raymond Toy replied 23 Aug 2001 with
1160 a partial explanation, but no fix has been found yet.
1163 Even in sbcl-0.pre7.x, which is supposed to be free of the old
1164 non-ANSI behavior of treating the function return type inferred
1165 from the current function definition as a declaration of the
1166 return type from any function of that name, the return type of NIL
1167 is attached to FOO in 120a above, and used to optimize code which
1171 There was some sort of screwup in handling of
1172 (IF (NOT (IGNORE-ERRORS ..))). E.g.
1174 (if (not (ignore-errors
1175 (make-pathname :host "foo" :directory "!bla" :name "bar")))
1177 (error "notunlessnot")))
1178 The (NOT (IGNORE-ERRORS ..)) form evaluates to T, so this should be
1179 printing "ok", but instead it's going to the ERROR. This problem
1180 seems to've been introduced by MNA's HANDLER-CASE patch (sbcl-devel
1181 2001-07-17) and as a workaround (put in sbcl-0.pre7.14.flaky4.12)
1182 I reverted back to the old weird HANDLER-CASE code. However, I
1183 think the problem looks like a compiler bug in handling RETURN-FROM,
1184 so I left the MNA-patched code in HANDLER-CASE (suppressed with
1185 #+NIL) and I'd like to go back to see whether this really is
1186 a compiler bug before I delete this BUGS entry.
1189 The *USE-IMPLEMENTATION-TYPES* hack causes bugs, particularly
1190 (IN-PACKAGE :SB-KERNEL)
1191 (TYPE= (SPECIFIER-TYPE '(VECTOR T))
1192 (SPECIFIER-TYPE '(VECTOR UNDEFTYPE)))
1193 Then because of this, the compiler bogusly optimizes
1194 (TYPEP #(11) '(SIMPLE-ARRAY UNDEF-TYPE 1))
1195 to T. Unfortunately, just setting *USE-IMPLEMENTATION-TYPES* to
1196 NIL around sbcl-0.pre7.14.flaky4.12 didn't work: the compiler complained
1197 about type mismatches (probably harmlessly, another instance of bug 117);
1198 and then cold init died with a segmentation fault.
1201 As of version 0.pre7.14, SBCL's implementation of MACROLET makes
1202 the entire lexical environment at the point of MACROLET available
1203 in the bodies of the macroexpander functions. In particular, it
1204 allows the function bodies (which run at compile time) to try to
1205 access lexical variables (which are only defined at runtime).
1206 It doesn't even issue a warning, which is bad.
1208 The SBCL behavior arguably conforms to the ANSI spec (since the
1209 spec says that the behavior is undefined, ergo anything conforms).
1210 However, it would be better to issue a compile-time error.
1211 Unfortunately I (WHN) don't see any simple way to detect this
1212 condition in order to issue such an error, so for the meantime
1213 SBCL just does this weird broken "conforming" thing.
1215 The ANSI standard says, in the definition of the special operator
1217 The macro-expansion functions defined by MACROLET are defined
1218 in the lexical environment in which the MACROLET form appears.
1219 Declarations and MACROLET and SYMBOL-MACROLET definitions affect
1220 the local macro definitions in a MACROLET, but the consequences
1221 are undefined if the local macro definitions reference any
1222 local variable or function bindings that are visible in that
1223 lexical environment.
1224 Then it seems to contradict itself by giving the example
1226 (macrolet ((fudge (z)
1227 ;The parameters x and flag are not accessible
1228 ; at this point; a reference to flag would be to
1229 ; the global variable of that name.
1230 ` (if flag (* ,z ,z) ,z)))
1231 ;The parameters x and flag are accessible here.
1235 The comment "a reference to flag would be to the global variable
1236 of the same name" sounds like good behavior for the system to have.
1237 but actual specification quoted above says that the actual behavior
1241 (as reported by Gabe Garza on cmucl-help 2001-09-21)
1243 (defun test-pred (x y)
1247 (func (lambda () x)))
1248 (print (eq func func))
1249 (print (test-pred func func))
1250 (delete func (list func))))
1251 Now calling (TEST-CASE) gives output
1254 (#<FUNCTION {500A9EF9}>)
1255 Evidently Python thinks of the lambda as a code transformation so
1256 much that it forgets that it's also an object.
1259 (reported by Dan Barlow sbcl-devel 2001-09-26)
1260 * (defun s () (make-string 10 :initial-element #\Space))
1269 "" <- ten ASCII NULs
1270 But other, non-#\Space values of INITIAL-ELEMENT work OK.
1273 KNOWN BUGS RELATED TO THE IR1 INTERPRETER
1275 (Now that the IR1 interpreter has gone away, these should be
1276 relatively straightforward to fix.)
1279 The system accepts DECLAIM in most places where DECLARE would be
1280 accepted, without even issuing a warning. ANSI allows this, but since
1281 it's fairly easy to mistype DECLAIM instead of DECLARE, and the
1282 meaning is rather different, and it's unlikely that the user
1283 has a good reason for doing DECLAIM not at top level, it would be
1284 good to issue a STYLE-WARNING when this happens. A possible
1285 fix would be to issue STYLE-WARNINGs for DECLAIMs not at top level,
1286 or perhaps to issue STYLE-WARNINGs for any EVAL-WHEN not at top level.
1287 [This is considered an IR1-interpreter-related bug because until
1288 EVAL-WHEN is rewritten, which won't happen until after the IR1
1289 interpreter is gone, the system's notion of what's a top-level form
1290 and what's not will remain too confused to fix this problem.]
1293 (another wishlist thing..) Reimplement DEFMACRO to be basically
1294 like DEFMACRO-MUNDANELY, just using EVAL-WHEN.