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, and (3) by their own reasoning, it looks as though
54 ANSI may have gotten it wrong. ANSI justifies this specification
56 The restriction against issuing a warning for type mismatches
57 between a slot-initform and the corresponding slot's :TYPE
58 option is necessary because a slot-initform must be specified
59 in order to specify slot options; in some cases, no suitable
61 However, in SBCL (as in CMU CL or, for that matter, any compiler
62 which really understands Common Lisp types) a suitable default
63 does exist, in all cases, because the compiler understands the
64 concept of functions which never return (i.e. has return type NIL).
65 Thus, as a portable workaround, you can use a call to some
66 known-never-to-return function as the default. E.g.
68 (BAR (ERROR "missing :BAR argument")
69 :TYPE SOME-TYPE-TOO-HAIRY-TO-CONSTRUCT-AN-INSTANCE-OF))
71 (DECLAIM (FTYPE (FUNCTION () NIL) MISSING-ARG))
72 (DEFUN REQUIRED-ARG () ; workaround for SBCL non-ANSI slot init typing
73 (ERROR "missing required argument"))
75 (BAR (REQUIRED-ARG) :TYPE TRICKY-TYPE-OF-SOME-SORT)
76 (BLETCH (REQUIRED-ARG) :TYPE TRICKY-TYPE-OF-SOME-SORT)
77 (N-REFS-SO-FAR 0 :TYPE (INTEGER 0)))
78 Such code should compile without complaint and work correctly either
79 on SBCL or on any other completely compliant Common Lisp system.
82 bogus warnings about undefined functions for magic functions like
83 SB!C::%%DEFUN and SB!C::%DEFCONSTANT when cross-compiling files
84 like src/code/float.lisp. Fixing this will probably require
85 straightening out enough bootstrap consistency issues that
86 the cross-compiler can run with *TYPE-SYSTEM-INITIALIZED*.
87 Instead, the cross-compiler runs in a slightly flaky state
88 which is sane enough to compile SBCL itself, but which is
89 also unstable in several ways, including its inability
90 to really grok function declarations.
93 The "compiling top-level form:" output ought to be condensed.
94 Perhaps any number of such consecutive lines ought to turn into a
95 single "compiling top-level forms:" line.
98 The way that the compiler munges types with arguments together
99 with types with no arguments (in e.g. TYPE-EXPAND) leads to
100 weirdness visible to the user:
101 (DEFTYPE FOO () 'FIXNUM)
103 (TYPEP 11 '(FOO)) => T, which seems weird
104 (TYPEP 11 'FIXNUM) => T
105 (TYPEP 11 '(FIXNUM)) signals an error, as it should
106 The situation is complicated by the presence of Common Lisp types
107 like UNSIGNED-BYTE (which can either be used in list form or alone)
108 so I'm not 100% sure that the behavior above is actually illegal.
109 But I'm 90+% sure, and the following related behavior,
111 treating the bare symbol AND as equivalent to '(AND), is specifically
112 forbidden (by the ANSI specification of the AND type).
115 It would be nice if the
117 (during macroexpansion)
118 said what macroexpansion was at fault, e.g.
120 (during macroexpansion of IN-PACKAGE,
121 during macroexpansion of DEFFOO)
124 (SUBTYPEP '(FUNCTION (T BOOLEAN) NIL)
125 '(FUNCTION (FIXNUM FIXNUM) NIL)) => T, T
126 (Also, when this is fixed, we can enable the code in PROCLAIM which
127 checks for incompatible FTYPE redeclarations.)
130 (I *think* this is a bug. It certainly seems like strange behavior. But
131 the ANSI spec is scary, dark, and deep.. -- WHN)
132 (FORMAT NIL "~,1G" 1.4) => "1. "
133 (FORMAT NIL "~3,1G" 1.4) => "1. "
136 from Marco Antoniotti on cmucl-imp mailing list 1 Mar 2000:
138 (setf (find-class 'ccc1) (find-class 'ccc))
139 (defmethod zut ((c ccc1)) 123)
140 In sbcl-0.7.1.13, this gives an error,
141 There is no class named CCC1.
142 DTC's recommended workaround from the mailing list 3 Mar 2000:
143 (setf (pcl::find-class 'ccc1) (pcl::find-class 'ccc))
146 Sometimes (SB-EXT:QUIT) fails with
147 Argh! maximum interrupt nesting depth (4096) exceeded, exiting
148 Process inferior-lisp exited abnormally with code 1
149 I haven't noticed a repeatable case of this yet.
152 The printer doesn't report closures very well. This is true in
156 #<Closure Over Function "DEFUN STRUCTURE-SLOT-ACCESSOR" {134D1A1}>
157 It would be nice to make closures have a settable name slot,
158 and make things like DEFSTRUCT and FLET, which create closures,
159 set helpful values into this slot.
162 And as long as we're wishing, it would be awfully nice if INSPECT could
163 also report on closures, telling about the values of the bound variables.
166 The compiler assumes that any time a function of declared FTYPE
167 doesn't signal an error, its arguments were of the declared type.
168 E.g. compiling and loading
169 (DECLAIM (OPTIMIZE (SAFETY 3)))
170 (DEFUN FACTORIAL (X) (GAMMA (1+ X)))
172 (DECLAIM (FTYPE (FUNCTION (UNSIGNED-BYTE)) FACTORIAL))
174 (COND ((> (FACTORIAL X) 1.0E6)
175 (FORMAT T "too big~%"))
177 (FORMAT T "exactly ~S~%" (FACTORIAL X)))
179 (FORMAT T "approximately ~S~%" (FACTORIAL X)))))
182 will cause the INTEGERP case to be selected, giving bogus output a la
184 This violates the "declarations are assertions" principle.
185 According to the ANSI spec, in the section "System Class FUNCTION",
186 this is a case of "lying to the compiler", but the lying is done
187 by the code which calls FACTORIAL with non-UNSIGNED-BYTE arguments,
188 not by the unexpectedly general definition of FACTORIAL. In any case,
189 "declarations are assertions" means that lying to the compiler should
190 cause an error to be signalled, and should not cause a bogus
191 result to be returned. Thus, the compiler should not assume
192 that arbitrary functions check their argument types. (It might
193 make sense to add another flag (CHECKED?) to DEFKNOWN to
194 identify functions which *do* check their argument types.)
195 (Also, verify that the compiler handles declared function
196 return types as assertions.)
199 TYPEP of VALUES types is sometimes implemented very inefficiently, e.g. in
200 (DEFTYPE INDEXOID () '(INTEGER 0 1000))
202 (DECLARE (TYPE INDEXOID X))
203 (THE (VALUES INDEXOID)
205 where the implementation of the type check in function FOO
206 includes a full call to %TYPEP. There are also some fundamental problems
207 with the interpretation of VALUES types (inherited from CMU CL, and
208 from the ANSI CL standard) as discussed on the cmucl-imp@cons.org
209 mailing list, e.g. in Robert Maclachlan's post of 21 Jun 2000.
212 The definitions of SIGCONTEXT-FLOAT-REGISTER and
213 %SET-SIGCONTEXT-FLOAT-REGISTER in x86-vm.lisp say they're not
214 supported on FreeBSD because the floating point state is not saved,
215 but at least as of FreeBSD 4.0, the floating point state *is* saved,
216 so they could be supported after all. Very likely
217 SIGCONTEXT-FLOATING-POINT-MODES could now be supported, too.
220 (as discussed by Douglas Crosher on the cmucl-imp mailing list ca.
221 Aug. 10, 2000): CMUCL currently interprets 'member as '(member); same
222 issue with 'union, 'and, 'or etc. So even though according to the
223 ANSI spec, bare 'MEMBER, 'AND, and 'OR are not legal types, CMUCL
224 (and now SBCL) interpret them as legal types.
227 a slew of floating-point-related errors reported by Peter Van Eynde
229 b: SBCL's value for LEAST-POSITIVE-SHORT-FLOAT is bogus, and
230 should probably be 1.4012985e-45. In SBCL,
231 (/ LEAST-POSITIVE-SHORT-FLOAT 2) returns a number smaller
232 than LEAST-POSITIVE-SHORT-FLOAT. Similar problems
233 exist for LEAST-NEGATIVE-SHORT-FLOAT, LEAST-POSITIVE-LONG-FLOAT,
234 and LEAST-NEGATIVE-LONG-FLOAT.
235 c: Many expressions generate floating infinity on x86/Linux:
240 PVE's regression tests want them to raise errors. sbcl-0.7.0.5
241 on x86/Linux generates the infinities instead. That might or
242 might not be conforming behavior, but it's also inconsistent,
243 which is almost certainly wrong. (Inconsistency: (/ 1 0.0)
244 should give the same result as (/ 1.0 0.0), but instead (/ 1 0.0)
245 generates SINGLE-FLOAT-POSITIVE-INFINITY and (/ 1.0 0.0)
247 d: (in section12.erg) various forms a la
248 (FLOAT 1 DOUBLE-FLOAT-EPSILON)
249 don't give the right behavior.
252 type safety errors reported by Peter Van Eynde July 25, 2000:
253 a: (COERCE (QUOTE (A B C)) (QUOTE (VECTOR * 4)))
255 In general lengths of array type specifications aren't
256 checked by COERCE, so it fails when the spec is
257 (VECTOR 4), (STRING 2), (SIMPLE-BIT-VECTOR 3), or whatever.
258 b: CONCATENATE has the same problem of not checking the length
259 of specified output array types. MAKE-SEQUENCE and MAP and
260 MERGE also have the same problem.
261 c: (COERCE 'AND 'FUNCTION) returns something related to
262 (MACRO-FUNCTION 'AND), but ANSI says it should raise an error.
263 g: (LOAD "*.lsp") should signal FILE-ERROR.
264 h: (MAKE-CONCATENATED-STREAM (MAKE-STRING-OUTPUT-STREAM))
265 should signal TYPE-ERROR.
266 i: MAKE-TWO-WAY-STREAM doesn't check that its arguments can
267 be used for input and output as needed. It should fail with
268 TYPE-ERROR when handed e.g. the results of
269 MAKE-STRING-INPUT-STREAM or MAKE-STRING-OUTPUT-STREAM in
270 the inappropriate positions, but doesn't.
271 k: READ-BYTE is supposed to signal TYPE-ERROR when its argument is
272 not a binary input stream, but instead cheerfully reads from
273 character streams, e.g. (MAKE-STRING-INPUT-STREAM "abc").
276 DEFCLASS bugs reported by Peter Van Eynde July 25, 2000:
277 a: (DEFCLASS FOO () (A B A)) should signal a PROGRAM-ERROR, and
279 b: (DEFCLASS FOO () (A B A) (:DEFAULT-INITARGS X A X B)) should
280 signal a PROGRAM-ERROR, and doesn't.
281 c: (DEFCLASS FOO07 NIL ((A :ALLOCATION :CLASS :ALLOCATION :CLASS))),
282 and other DEFCLASS forms with duplicate specifications in their
283 slots, should signal a PROGRAM-ERROR, and doesn't.
284 d: (DEFGENERIC IF (X)) should signal a PROGRAM-ERROR, but instead
285 causes a COMPILER-ERROR.
288 SYMBOL-MACROLET bugs reported by Peter Van Eynde July 25, 2000:
289 a: (SYMBOL-MACROLET ((T TRUE)) ..) should probably signal
290 PROGRAM-ERROR, but SBCL accepts it instead.
291 b: SYMBOL-MACROLET should refuse to bind something which is
292 declared as a global variable, signalling PROGRAM-ERROR.
293 c: SYMBOL-MACROLET should signal PROGRAM-ERROR if something
294 it binds is declared SPECIAL inside.
297 miscellaneous errors reported by Peter Van Eynde July 25, 2000:
299 (DEFGENERIC FOO02 (X))
300 (DEFMETHOD FOO02 ((X NUMBER)) T)
301 (LET ((M (FIND-METHOD (FUNCTION FOO02)
303 (LIST (FIND-CLASS (QUOTE NUMBER))))))
304 (REMOVE-METHOD (FUNCTION FOO02) M)
305 (DEFGENERIC FOO03 (X))
306 (ADD-METHOD (FUNCTION FOO03) M)))
307 should give an error, but SBCL allows it.
308 b: READ should probably return READER-ERROR, not the bare
309 arithmetic error, when input a la "1/0" or "1e1000" causes
313 It has been reported (e.g. by Peter Van Eynde) that there are
314 several metaobject protocol "errors". (In order to fix them, we might
315 need to document exactly what metaobject protocol specification
316 we're following -- the current code is just inherited from PCL.)
319 The implementation of #'+ returns its single argument without
320 type checking, e.g. (+ "illegal") => "illegal".
323 The debugger LIST-LOCATIONS command doesn't work properly.
326 Compiling and loading
327 (DEFUN FAIL (X) (THROW 'FAIL-TAG X))
329 then requesting a BACKTRACE at the debugger prompt gives no information
330 about where in the user program the problem occurred.
333 The compiler is supposed to do type inference well enough that
336 ((SIMPLE-ARRAY SINGLE-FLOAT)
338 (DECLARE (TYPE (SIMPLE-ARRAY SINGLE-FLOAT) X))
341 is redundant. However, as reported by Juan Jose Garcia Ripoll for
342 CMU CL, it sometimes doesn't. Adding declarations is a pretty good
343 workaround for the problem for now, but can't be done by the TYPECASE
344 macros themselves, since it's too hard for the macro to detect
345 assignments to the variable within the clause.
346 Note: The compiler *is* smart enough to do the type inference in
347 many cases. This case, derived from a couple of MACROEXPAND-1
348 calls on Ripoll's original test case,
350 (DECLARE (OPTIMIZE SPEED (SAFETY 0)))
351 (COND ((TYPEP A '(SIMPLE-ARRAY SINGLE-FLOAT)) NIL
352 (LET ((LENGTH (ARRAY-TOTAL-SIZE A)))
353 (LET ((I 0) (G2554 LENGTH))
354 (DECLARE (TYPE REAL G2554) (TYPE REAL I))
357 (WHEN (>= I G2554) (GO SB-LOOP::END-LOOP))
358 (SETF (ROW-MAJOR-AREF A I) (- (ROW-MAJOR-AREF A I)))
359 (GO SB-LOOP::NEXT-LOOP)
360 SB-LOOP::END-LOOP))))))
361 demonstrates the problem; but the problem goes away if the TAGBODY
362 and GO forms are removed (leaving the SETF in ordinary, non-looping
363 code), or if the TAGBODY and GO forms are retained, but the
364 assigned value becomes 0.0 instead of (- (ROW-MAJOR-AREF A I)).
367 Paul Werkowski wrote on cmucl-imp@cons.org 2000-11-15
368 I am looking into this problem that showed up on the cmucl-help
369 list. It seems to me that the "implementation specific environment
370 hacking functions" found in pcl/walker.lisp are completely messed
371 up. The good thing is that they appear to be barely used within
372 PCL and the munged environment object is passed to cmucl only
373 in calls to macroexpand-1, which is probably why this case fails.
374 SBCL uses essentially the same code, so if the environment hacking
375 is screwed up, it affects us too.
378 Using the pretty-printer from the command prompt gives funny
379 results, apparently because the pretty-printer doesn't know
380 about user's command input, including the user's carriage return
381 that the user, and therefore the pretty-printer thinks that
382 the new output block should start indented 2 or more characters
383 rightward of the correct location.
386 (probably related to bug #70; maybe related to bug #109)
387 As reported by Carl Witty on submit@bugs.debian.org 1999-05-08,
389 (in-package "CL-USER")
390 (defun equal-terms (termx termy)
392 ((alpha-equal-bound-term-lists (listx listy)
393 (or (and (null listx) (null listy))
395 (let ((bindings-x (bindings-of-bound-term (car listx)))
396 (bindings-y (bindings-of-bound-term (car listy))))
397 (if (and (null bindings-x) (null bindings-y))
398 (alpha-equal-terms (term-of-bound-term (car listx))
399 (term-of-bound-term (car listy)))
400 (and (= (length bindings-x) (length bindings-y))
402 (enter-binding-pairs (bindings-of-bound-term (car listx))
403 (bindings-of-bound-term (car listy)))
404 (alpha-equal-terms (term-of-bound-term (car listx))
405 (term-of-bound-term (car listy)))
406 (exit-binding-pairs (bindings-of-bound-term (car listx))
407 (bindings-of-bound-term (car listy)))))))
408 (alpha-equal-bound-term-lists (cdr listx) (cdr listy)))))
410 (alpha-equal-terms (termx termy)
411 (if (and (variable-p termx)
413 (equal-bindings (id-of-variable-term termx)
414 (id-of-variable-term termy))
415 (and (equal-operators-p (operator-of-term termx) (operator-of-term termy))
416 (alpha-equal-bound-term-lists (bound-terms-of-term termx)
417 (bound-terms-of-term termy))))))
421 (with-variable-invocation (alpha-equal-terms termx termy))))))
422 causes an assertion failure
423 The assertion (EQ (C::LAMBDA-TAIL-SET C::CALLER)
424 (C::LAMBDA-TAIL-SET (C::LAMBDA-HOME C::CALLEE))) failed.
426 Bob Rogers reports (1999-07-28 on cmucl-imp@cons.org) a smaller test
427 case with the same problem:
428 (defun parse-fssp-alignment ()
429 ;; Given an FSSP alignment file named by the argument . . .
430 (labels ((get-fssp-char ()
434 ;; Stub body, enough to tickle the bug.
435 (list (read-fssp-char)
439 ANSI specifies that the RESULT-TYPE argument of CONCATENATE must be
440 a subtype of SEQUENCE, but CONCATENATE doesn't check this properly:
441 (CONCATENATE 'SIMPLE-ARRAY #(1 2) '(3)) => #(1 2 3)
442 This also leads to funny behavior when derived type specifiers
443 are used, as originally reported by Milan Zamazal for CMU CL (on the
444 Debian bugs mailing list (?) 2000-02-27), then reported by Martin
445 Atzmueller for SBCL (2000-10-01 on sbcl-devel@lists.sourceforge.net):
446 (DEFTYPE FOO () 'SIMPLE-ARRAY)
447 (CONCATENATE 'FOO #(1 2) '(3))
448 => #<ARRAY-TYPE SIMPLE-ARRAY> is a bad type specifier for
450 The derived type specifier FOO should act the same way as the
451 built-in type SIMPLE-ARRAY here, but it doesn't. That problem
452 doesn't seem to exist for sequence types:
453 (DEFTYPE BAR () 'SIMPLE-VECTOR)
454 (CONCATENATE 'BAR #(1 2) '(3)) => #(1 2 3)
457 As reported by Winton Davies on a CMU CL mailing list 2000-01-10,
458 and reported for SBCL by Martin Atzmueller 2000-10-20: (TRACE GETHASH)
459 crashes SBCL. In general tracing anything which is used in the
460 implementation of TRACE is likely to have the same problem.
463 As reported by Daniel Solaz on cmucl-help@cons.org 2000-11-23,
464 SXHASH returns the same value for all non-STRUCTURE-OBJECT instances,
465 notably including all PCL instances. There's a limit to how much
466 SXHASH can do to return unique values for instances, but at least
467 it should probably look at the class name, the way that it does
468 for STRUCTURE-OBJECTs.
471 (probably related to bug #65; maybe related to bug #109)
472 The compiler doesn't like &OPTIONAL arguments in LABELS and FLET
474 (DEFUN FIND-BEFORE (ITEM SEQUENCE &KEY (TEST #'EQL))
475 (LABELS ((FIND-ITEM (OBJ SEQ TEST &OPTIONAL (VAL NIL))
476 (LET ((ITEM (FIRST SEQ)))
479 ((FUNCALL TEST OBJ ITEM)
482 (FIND-ITEM OBJ (REST SEQ) TEST (NCONC VAL `(,ITEM))))))))
483 (FIND-ITEM ITEM SEQUENCE TEST)))
484 from David Young's bug report on cmucl-help@cons.org 30 Nov 2000
485 causes sbcl-0.6.9 to fail with
486 error in function SB-KERNEL:ASSERT-ERROR:
487 The assertion (EQ (SB-C::LAMBDA-TAIL-SET SB-C::CALLER)
488 (SB-C::LAMBDA-TAIL-SET
489 (SB-C::LAMBDA-HOME SB-C::CALLEE))) failed.
492 (DECLAIM (OPTIMIZE ..)) doesn't work. E.g. even after
493 (DECLAIM (OPTIMIZE (SPEED 3))), things are still optimized with
494 the previous SPEED policy. This bug will probably get fixed in
495 0.6.9.x in a general cleanup of optimization policy.
498 (DECLAIM (OPTIMIZE ..)) doesn't work properly inside LOCALLY forms.
501 As reported by Martin Atzmueller on sbcl-devel 26 Dec 2000,
502 ANSI says that WITH-OUTPUT-TO-STRING should have a keyword
503 :ELEMENT-TYPE, but in sbcl-0.6.9 this is not defined for
504 WITH-OUTPUT-TO-STRING.
507 ANSI says in one place that type declarations can be abbreviated even
508 when the type name is not a symbol, e.g.
509 (DECLAIM ((VECTOR T) *FOOVECTOR*))
510 SBCL doesn't support this. But ANSI says in another place that this
511 isn't allowed. So it's not clear this is a bug after all. (See the
512 e-mail on cmucl-help@cons.org on 2001-01-16 and 2001-01-17 from WHN
516 as pointed out by Dan Barlow on sbcl-devel 2000-07-02:
517 The PICK-TEMPORARY-FILE-NAME utility used by LOAD-FOREIGN uses
518 an easily guessable temporary filename in a way which might open
519 applications using LOAD-FOREIGN to hijacking by malicious users
520 on the same machine. Incantations for doing this safely are
521 floating around the net in various "how to write secure programs
522 despite Unix" documents, and it would be good to (1) fix this in
523 LOAD-FOREIGN, and (2) hunt for any other code which uses temporary
524 files and make it share the same new safe logic.
527 Functions are assigned names based on the context in which they're
528 defined. This is less than ideal for the functions which are
529 used to implement CLOS methods. E.g. the output of
530 (DESCRIBE 'PRINT-OBJECT) lists functions like
531 #<FUNCTION "DEF!STRUCT (TRACE-INFO (:MAKE-LOAD-FORM-FUN SB-KERNEL:JUST-DUMP-IT-NORMALLY) (:PRINT-OBJECT #))" {1020E49}>
533 #<FUNCTION "MACROLET ((FORCE-DELAYED-DEF!METHODS NIL #))" {1242871}>
534 It would be better if these functions' names always identified
535 them as methods, and identified their generic functions and
539 RANDOM-INTEGER-EXTRA-BITS=10 may not be large enough for the RANDOM
540 RNG to be high quality near RANDOM-FIXNUM-MAX; it looks as though
541 the mean of the distribution can be systematically O(0.1%) wrong.
542 Just increasing R-I-E-B is probably not a good solution, since
543 it would decrease efficiency more than is probably necessary. Perhaps
544 using some sort of accept/reject method would be better.
547 Internally the compiler sometimes evaluates
548 (sb-kernel:type/= (specifier-type '*) (specifier-type t))
549 (I stumbled across this when I added an
550 (assert (not (eq type1 *wild-type*)))
551 in the NAMED :SIMPLE-= type method.) '* isn't really a type, and
552 in a type context should probably be translated to T, and so it's
553 probably wrong to ask whether it's equal to the T type and then (using
554 the EQ type comparison in the NAMED :SIMPLE-= type method) return NIL.
555 (I haven't tried to investigate this bug enough to guess whether
556 there might be any user-level symptoms.)
559 a latent cross-compilation/bootstrapping bug: The cross-compilation
560 host's CL:CHAR-CODE-LIMIT is used in target code in readtable.lisp
561 and possibly elsewhere. Instead, we should use the target system's
562 CHAR-CODE-LIMIT. This will probably cause problems if we try to
563 bootstrap on a system which uses a different value of CHAR-CODE-LIMIT
567 Inconsistencies between derived and declared VALUES return types for
568 DEFUN aren't checked very well. E.g. the logic which successfully
569 catches problems like
570 (declaim (ftype (function (fixnum) float) foo))
572 (declare (type integer x))
573 (values x)) ; wrong return type, detected, gives warning, good!
575 (declaim (ftype (function (t) (values t t)) bar))
577 (values x)) ; wrong number of return values, no warning, bad!
578 The cause of this is seems to be that (1) the internal function
579 VALUES-TYPES-EQUAL-OR-INTERSECT used to make the check handles its
580 arguments symmetrically, and (2) when the type checking code was
581 written back when when SBCL's code was still CMU CL, the intent
583 (declaim (ftype (function (t) t) bar))
585 (values x x)) ; wrong number of return values; should give warning?
586 not be warned for, because a two-valued return value is considered
587 to be compatible with callers who expects a single value to be
588 returned. That intent is probably not appropriate for modern ANSI
589 Common Lisp, but fixing this might be complicated because of other
590 divergences between auld-style and new-style handling of
591 multiple-VALUES types. (Some issues related to this were discussed
592 on cmucl-imp at some length sometime in 2000.)
595 The facility for dumping a running Lisp image to disk gets confused
596 when run without the PURIFY option, and creates an unnecessarily large
597 core file (apparently representing memory usage up to the previous
598 high-water mark). Moreover, when the file is loaded, it confuses the
599 GC, so that thereafter memory usage can never be reduced below that
603 The TRACE facility can't be used on some kinds of functions.
604 (Basically, the breakpoint facility was incompletely implemented
605 in the X86 port of CMU CL, and hasn't been fixed in SBCL.)
608 In sbcl-0.6.11.41 (and in all earlier SBCL, and in CMU
609 CL), out-of-line structure slot setters are horribly inefficient
610 whenever the type of the slot is declared, because out-of-line
611 structure slot setters are implemented as closures to save space,
612 so the compiler doesn't compile the type test into code, but
613 instead just saves the type in a lexical closure and interprets it
615 A proper solution involves deciding whether it's really worth
616 saving space by implementing structure slot accessors as closures.
617 (If it's not worth it, the problem vanishes automatically. If it
618 is worth it, there are hacks we could use to force type tests to
619 be compiled anyway, and even shared. E.g. we could implement
620 an EQUAL hash table mapping from types to compiled type tests,
621 and save the appropriate compiled type test as part of each lexical
622 closure; or we could make the lexical closures be placeholders
623 which overwrite their old definition as a lexical closure with
624 a new compiled definition the first time that they're called.)
625 As a workaround for the problem, #'(SETF FOO) expressions can
626 be replaced with (EFFICIENT-SETF-FUNCTION FOO), where
627 (defmacro efficient-setf-function (place-function-name)
628 (or #+sbcl (and (sb-impl::info :function :accessor-for place-function-name)
629 ;; a workaround for the problem, encouraging the
630 ;; inline expansion of the structure accessor, so
631 ;; that the compiler can optimize its type test
632 (let ((new-value (gensym "NEW-VALUE-"))
633 (structure-value (gensym "STRUCTURE-VALUE-")))
634 `(lambda (,new-value ,structure-value)
635 (setf (,place-function-name ,structure-value)
637 ;; no problem, can just use the ordinary expansion
638 `(function (setf ,place-function-name))))
641 There's apparently a bug in CEILING optimization which caused
642 Douglas Crosher to patch the CMU CL version. Martin Atzmueller
643 applied the patches to SBCL and they didn't seem to cause problems
644 (as reported sbcl-devel 2001-05-04). However, since the patches
645 modify nontrivial code which was apparently written incorrectly
646 the first time around, until regression tests are written I'm not
647 comfortable merging the patches in the CVS version of SBCL.
650 As reported by Arthur Lemmens sbcl-devel 2001-05-05, ANSI
651 requires that SYMBOL-MACROLET refuse to rebind special variables,
652 but SBCL doesn't do this. (Also as reported by AL in the same
653 message, SBCL depended on this nonconforming behavior to build
654 itself, because of the way that **CURRENT-SEGMENT** was implemented.
655 As of sbcl-0.7.3.x, this dependence on the nonconforming behavior
656 has been fixed, but the nonconforming behavior remains.)
659 (DESCRIBE 'SB-ALIEN:DEF-ALIEN-TYPE) reports the macro argument list
663 in #<PACKAGE "SB-ALIEN">.
664 Macro-function: #<FUNCTION "DEF!MACRO DEF-ALIEN-TYPE" {19F4A39}>
665 Macro arguments: (#:whole-470 #:environment-471)
666 On Sat, May 26, 2001 09:45:57 AM CDT it was compiled from:
667 /usr/stuff/sbcl/src/code/host-alieneval.lisp
668 Created: Monday, March 12, 2001 07:47:43 AM CST
671 (TIME (ROOM T)) reports more than 200 Mbytes consed even for
672 a clean, just-started SBCL system. And it seems to be right:
673 (ROOM T) can bring a small computer to its knees for a *long*
674 time trying to GC afterwards. Surely there's some more economical
675 way to implement (ROOM T).
678 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
680 ;;; This file fails to compile.
681 ;;; Maybe this bug is related to bugs #65, #70 in the BUGS file.
682 (in-package :cl-user)
688 ;; Uncomment and it works
691 In SBCL 0.6.12.42, the problem is
692 internal error, failed AVER:
693 "(COMMON-LISP:EQ (SB!C::LAMBDA-TAIL-SET SB!C::CALLER)
694 (SB!C::LAMBDA-TAIL-SET (SB!C::LAMBDA-HOME SB!C::CALLEE)))"
697 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
699 ;;; The compiler is flushing the argument type test, and the default
700 ;;; case in the cond, so that calling with say a fixnum 0 causes a
702 (declaim (optimize (safety 2) (speed 3)))
704 (declare (type (or string stream) x))
705 (cond ((typep x 'string) 'string)
706 ((typep x 'stream) 'stream)
709 The symptom in sbcl-0.6.12.42 on OpenBSD is actually (TST 0)=>STREAM
710 (not the SIGBUS reported in the comment) but that's broken too;
711 type declarations are supposed to be treated as assertions unless
712 SAFETY 0, so we should be getting a TYPE-ERROR.
715 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
717 (in-package :cl-user)
718 ;;; From: David Gadbois <gadbois@cyc.com>
720 ;;; Logical pathnames aren't externalizable.
722 (let ((tempfile "/tmp/test.lisp"))
723 (setf (logical-pathname-translations "XXX")
724 '(("XXX:**;*.*" "/tmp/**/*.*")))
725 (with-open-file (out tempfile :direction :output)
726 (write-string "(defvar *path* #P\"XXX:XXX;FOO.LISP\")" out))
727 (compile-file tempfile))
728 The error message in sbcl-0.6.12.42 is
730 ; (while making load form for #<SB-IMPL::LOGICAL-HOST "XXX">)
731 ; A logical host can't be dumped as a constant: #<SB-IMPL::LOGICAL-HOST "XXX">
734 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
736 (in-package :cl-user)
737 ;;; The following invokes a compiler error.
738 (declaim (optimize (speed 2) (debug 3)))
741 (unwind-protect nil)))
745 The error message in sbcl-0.6.12.42 is
746 internal error, failed AVER:
747 "(COMMON-LISP:EQ (SB!C::TN-ENVIRONMENT SB!C:TN) SB!C::TN-ENV)"
750 When the compiler inline expands functions, it may be that different
751 kinds of return values are generated from different code branches.
752 E.g. an inline expansion of POSITION generates integer results
753 from one branch, and NIL results from another. When that inline
754 expansion is used in a context where only one of those results
757 (aref *a1* (position x *a2*)))
758 and the compiler can't prove that the unacceptable branch is
759 never taken, then bogus type mismatch warnings can be generated.
760 If you need to suppress the type mismatch warnings, you can
761 suppress the inline expansion,
763 #+sbcl (declare (notinline position)) ; to suppress bug 117 bogowarnings
764 (aref *a1* (position x *a2*)))
765 or, sometimes, suppress them by declaring the result to be of an
768 (aref *a1* (the integer (position x *a2*))))
770 This is not a new compiler problem in 0.7.0, but the new compiler
771 transforms for FIND, POSITION, FIND-IF, and POSITION-IF make it
772 more conspicuous. If you don't need performance from these functions,
773 and the bogus warnings are a nuisance for you, you can return to
774 your pre-0.7.0 state of grace with
775 #+sbcl (declaim (notinline find position find-if position-if)) ; bug 117..
778 as reported by Eric Marsden on cmucl-imp@cons.org 2001-08-14:
779 (= (FLOAT 1 DOUBLE-FLOAT-EPSILON)
780 (+ (FLOAT 1 DOUBLE-FLOAT-EPSILON) DOUBLE-FLOAT-EPSILON)) => T
781 when of course it should be NIL. (He says it only fails for X86,
782 not SPARC; dunno about Alpha.)
784 Also, "the same problem exists for LONG-FLOAT-EPSILON,
785 DOUBLE-FLOAT-NEGATIVE-EPSILON, LONG-FLOAT-NEGATIVE-EPSILON (though
786 for the -negative- the + is replaced by a - in the test)."
788 Raymond Toy comments that this is tricky on the X86 since its FPU
789 uses 80-bit precision internally.
792 The compiler incorrectly figures the return type of
793 (DEFUN FOO (FRAME UP-FRAME)
800 This problem exists in CMU CL 18c too. When I reported it on
801 cmucl-imp@cons.org, Raymond Toy replied 23 Aug 2001 with
802 a partial explanation, but no fix has been found yet.
805 Even in sbcl-0.pre7.x, which is supposed to be free of the old
806 non-ANSI behavior of treating the function return type inferred
807 from the current function definition as a declaration of the
808 return type from any function of that name, the return type of NIL
809 is attached to FOO in 120a above, and used to optimize code which
813 There was some sort of screwup in handling of
814 (IF (NOT (IGNORE-ERRORS ..))). E.g.
816 (if (not (ignore-errors
817 (make-pathname :host "foo" :directory "!bla" :name "bar")))
819 (error "notunlessnot")))
820 The (NOT (IGNORE-ERRORS ..)) form evaluates to T, so this should be
821 printing "ok", but instead it's going to the ERROR. This problem
822 seems to've been introduced by MNA's HANDLER-CASE patch (sbcl-devel
823 2001-07-17) and as a workaround (put in sbcl-0.pre7.14.flaky4.12)
824 I reverted back to the old weird HANDLER-CASE code. However, I
825 think the problem looks like a compiler bug in handling RETURN-FROM,
826 so I left the MNA-patched code in HANDLER-CASE (suppressed with
827 #+NIL) and I'd like to go back to see whether this really is
828 a compiler bug before I delete this BUGS entry.
831 The *USE-IMPLEMENTATION-TYPES* hack causes bugs, particularly
832 (IN-PACKAGE :SB-KERNEL)
833 (TYPE= (SPECIFIER-TYPE '(VECTOR T))
834 (SPECIFIER-TYPE '(VECTOR UNDEFTYPE)))
835 Then because of this, the compiler bogusly optimizes
836 (TYPEP #(11) '(SIMPLE-ARRAY UNDEF-TYPE 1))
837 to T. Unfortunately, just setting *USE-IMPLEMENTATION-TYPES* to
838 NIL around sbcl-0.pre7.14.flaky4.12 didn't work: the compiler complained
839 about type mismatches (probably harmlessly, another instance of bug 117);
840 and then cold init died with a segmentation fault.
843 As of version 0.pre7.14, SBCL's implementation of MACROLET makes
844 the entire lexical environment at the point of MACROLET available
845 in the bodies of the macroexpander functions. In particular, it
846 allows the function bodies (which run at compile time) to try to
847 access lexical variables (which are only defined at runtime).
848 It doesn't even issue a warning, which is bad.
850 The SBCL behavior arguably conforms to the ANSI spec (since the
851 spec says that the behavior is undefined, ergo anything conforms).
852 However, it would be better to issue a compile-time error.
853 Unfortunately I (WHN) don't see any simple way to detect this
854 condition in order to issue such an error, so for the meantime
855 SBCL just does this weird broken "conforming" thing.
857 The ANSI standard says, in the definition of the special operator
859 The macro-expansion functions defined by MACROLET are defined
860 in the lexical environment in which the MACROLET form appears.
861 Declarations and MACROLET and SYMBOL-MACROLET definitions affect
862 the local macro definitions in a MACROLET, but the consequences
863 are undefined if the local macro definitions reference any
864 local variable or function bindings that are visible in that
866 Then it seems to contradict itself by giving the example
868 (macrolet ((fudge (z)
869 ;The parameters x and flag are not accessible
870 ; at this point; a reference to flag would be to
871 ; the global variable of that name.
872 ` (if flag (* ,z ,z) ,z)))
873 ;The parameters x and flag are accessible here.
877 The comment "a reference to flag would be to the global variable
878 of the same name" sounds like good behavior for the system to have.
879 but actual specification quoted above says that the actual behavior
883 (as reported by Gabe Garza on cmucl-help 2001-09-21)
885 (defun test-pred (x y)
889 (func (lambda () x)))
890 (print (eq func func))
891 (print (test-pred func func))
892 (delete func (list func))))
893 Now calling (TEST-CASE) gives output
896 (#<FUNCTION {500A9EF9}>)
897 Evidently Python thinks of the lambda as a code transformation so
898 much that it forgets that it's also an object.
904 The DEFSTRUCT section of the ANSI spec, in the :CONC-NAME section,
905 specifies a precedence rule for name collisions between slot accessors of
906 structure classes related by inheritance. As of 0.7.0, SBCL still
910 insufficient syntax checking in MACROLET:
912 (macrolet ((defmacro bar (z) `(+ z z)))
914 shouldn't compile without error (because of the extra DEFMACRO symbol).
917 As of sbcl-0.pre7.86.flaky7.3, the cross-compiler, and probably
918 the CL:COMPILE function (which is based on the same %COMPILE
919 mechanism) get confused by
921 (labels ((sxhash-number (x)
923 (fixnum (sxhash x)) ; through DEFTRANSFORM
924 (integer (sb!bignum:sxhash-bignum x))
925 (single-float (sxhash x)) ; through DEFTRANSFORM
926 (double-float (sxhash x)) ; through DEFTRANSFORM
927 #!+long-float (long-float (error "stub: no LONG-FLOAT"))
928 (ratio (let ((result 127810327))
929 (declare (type fixnum result))
930 (mixf result (sxhash-number (numerator x)))
931 (mixf result (sxhash-number (denominator x)))
933 (complex (let ((result 535698211))
934 (declare (type fixnum result))
935 (mixf result (sxhash-number (realpart x)))
936 (mixf result (sxhash-number (imagpart x)))
938 (sxhash-recurse (x &optional (depthoid +max-hash-depthoid+))
939 (declare (type index depthoid))
943 (mix (sxhash-recurse (car x) (1- depthoid))
944 (sxhash-recurse (cdr x) (1- depthoid)))
947 (if (typep x 'structure-object)
949 (sxhash ; through DEFTRANSFORM
950 (class-name (layout-class (%instance-layout x)))))
952 (symbol (sxhash x)) ; through DEFTRANSFORM
953 (number (sxhash-number x))
956 (simple-string (sxhash x)) ; through DEFTRANSFORM
957 (string (%sxhash-substring x))
958 (bit-vector (let ((result 410823708))
959 (declare (type fixnum result))
960 (dotimes (i (min depthoid (length x)))
961 (mixf result (aref x i)))
963 (t (logxor 191020317 (sxhash (array-rank x))))))
966 (sxhash (char-code x)))) ; through DEFTRANSFORM
969 complaining "function called with two arguments, but wants exactly
970 one" about SXHASH-RECURSE. (This might not be strictly a new bug,
971 since IIRC post-fork CMU CL has also had problems with &OPTIONAL
972 arguments in FLET/LABELS: it might be an old Python bug which is
973 only exercised by the new arrangement of the SBCL compiler.)
976 Ideally, uninterning a symbol would allow it, and its associated
977 FDEFINITION and PROCLAIM data, to be reclaimed by the GC. However,
978 at least as of sbcl-0.7.0, this isn't the case. Information about
979 FDEFINITIONs and PROCLAIMed properties is stored in globaldb.lisp
980 essentially in ordinary (non-weak) hash tables keyed by symbols.
981 Thus, once a system has an entry in this system, it tends to live
982 forever, even when it is uninterned and all other references to it
986 (reported by Arnaud Rouanet on cmucl-imp 2001-12-18)
987 (defmethod foo ((x integer))
989 (defmethod foo :around ((x integer))
992 Now (FOO 3) should return 3, but instead it returns 4.
995 (SB-DEBUG:BACKTRACE) output should start with something
996 including the name BACKTRACE, not (as in 0.pre7.88)
997 just "0: (\"hairy arg processor\" ...)". Until about
998 sbcl-0.pre7.109, the names in BACKTRACE were all screwed
999 up compared to the nice useful names in sbcl-0.6.13.
1000 Around sbcl-0.pre7.109, they were mostly fixed by using
1001 NAMED-LAMBDA to implement DEFUN. However, there are still
1002 some screwups left, e.g. as of sbcl-0.pre7.109, there are
1003 still some functions named "hairy arg processor" and
1004 "SB-INT:&MORE processor".
1007 (reported by Alexey Dejneka sbcl-devel 2002-01-03)
1009 SUBTYPEP does not work well with redefined classes:
1011 * (defclass a () ())
1013 * (defclass b () ())
1018 * (defclass b (a) ())
1023 * (defclass b () ())
1031 This is probably due to underzealous clearing of the type caches; a
1032 brute-force solution in that case would be to make a defclass expand
1033 into something that included a call to SB-KERNEL::CLEAR-TYPE-CACHES,
1034 but there may be a better solution.
1037 Pretty-printing nested backquotes doesn't work right, as
1038 reported by Alexey Dejneka sbcl-devel 2002-01-13:
1040 ``(FOO SB-IMPL::BACKQ-COMMA-AT S)
1041 * (lisp-implementation-version)
1045 (as reported by Lynn Quam on cmucl-imp ca. 2002-01-16)
1046 %NATURALIZE-C-STRING conses a lot, like 16 bytes per byte
1047 of the naturalized string. We could probably port the patches
1048 from the cmucl-imp mailing list.
1051 (reported by Jesse Bouwman 2001-10-24 through the unfortunately
1052 prominent SourceForge web/db bug tracking system, which is
1053 unfortunately not a reliable way to get a timely response from
1054 the SBCL maintainers)
1055 In the course of trying to build a test case for an
1056 application error, I encountered this behavior:
1057 If you start up sbcl, and then lay on CTRL-C for a
1058 minute or two, the lisp process will eventually say:
1059 %PRIMITIVE HALT called; the party is over.
1060 and throw you into the monitor. If I start up lisp,
1061 attach to the process with strace, and then do the same
1062 (abusive) thing, I get instead:
1063 access failure in heap page not marked as write-protected
1064 and the monitor again. I don't know enough to have the
1065 faintest idea of what is going on here.
1066 This is with sbcl 6.12, uname -a reports:
1067 Linux prep 2.2.19 #4 SMP Tue Apr 24 13:59:52 CDT 2001 i686 unknown
1068 I (WHN) have verified that the same thing occurs on sbcl-0.pre7.141
1069 under OpenBSD 2.9 on my X86 laptop. Do be patient when you try it:
1070 it took more than two minutes (but less than five) for me.
1073 (This was once known as IR1-4, but it lived on even after the
1074 IR1 interpreter went to the big bit bucket in the sky.)
1075 The system accepts DECLAIM in most places where DECLARE would be
1076 accepted, without even issuing a warning. ANSI allows this, but since
1077 it's fairly easy to mistype DECLAIM instead of DECLARE, and the
1078 meaning is rather different, and it's unlikely that the user
1079 has a good reason for doing DECLAIM not at top level, it would be
1080 good to issue a STYLE-WARNING when this happens. A possible
1081 fix would be to issue STYLE-WARNINGs for DECLAIMs not at top level,
1082 or perhaps to issue STYLE-WARNINGs for any EVAL-WHEN not at top level.
1083 [This is considered an IR1-interpreter-related bug because until
1084 EVAL-WHEN is rewritten, which won't happen until after the IR1
1085 interpreter is gone, the system's notion of what's a top-level form
1086 and what's not will remain too confused to fix this problem.]
1089 ANSI allows types `(COMPLEX ,FOO) to use very hairy values for
1090 FOO, e.g. (COMPLEX (AND REAL (SATISFIES ODDP))). The old CMU CL
1091 COMPLEX implementation didn't deal with this, and hasn't been
1092 upgraded to do so. (This doesn't seem to be a high priority
1093 conformance problem, since seems hard to construct useful code
1097 Floating point errors are reported poorly. E.g. on x86 OpenBSD
1100 debugger invoked on condition of type SB-KERNEL:FLOATING-POINT-EXCEPTION:
1101 An arithmetic error SB-KERNEL:FLOATING-POINT-EXCEPTION was signalled.
1102 No traps are enabled? How can this be?
1103 It should be possible to be much more specific (overflow, division
1104 by zero, etc.) and of course the "How can this be?" should be fixable.
1107 In sbcl-0.7.1.3 on x86, COMPILE-FILE on the file
1108 (in-package :cl-user)
1111 (defstruct foo bar bletch)
1113 (labels ((kidify1 (kid)
1118 (m+ (frobnicate kid)
1121 (declare (inline kid-frob))
1124 (the simple-vector (foo-bar perd)))))
1126 debugger invoked on condition of type TYPE-ERROR:
1127 The value NIL is not of type SB-C::NODE.
1128 The location of this failure has moved around as various related
1129 issues were cleaned up. As of sbcl-0.7.1.9, it occurs in
1130 NODE-BLOCK called by LAMBDA-COMPONENT called by IR2-CONVERT-CLOSURE.
1133 (essentially the same problem as a CMU CL bug reported by Martin
1134 Cracauer on cmucl-imp 2002-02-19)
1135 There is a hole in structure slot type checking. Compiling and LOADing
1136 (declaim (optimize safety))
1138 (bla 0 :type fixnum))
1140 (let ((foo (make-foo)))
1141 (setf (foo-bla foo) '(1 . 1))
1142 (format t "Is ~a of type ~a a cons? => ~a~%"
1144 (type-of (foo-bla foo))
1145 (consp (foo-bla foo)))))
1147 should signal an error, but in sbcl-0.7.1.21 instead gives the output
1148 Is (1 . 1) of type CONS a cons? => NIL
1149 without signalling an error.
1152 There's some sort of problem with aborting back out of the debugger
1153 after a %DETECT-STACK-EXHAUSTION error in sbcl-0.7.1.38. In some cases
1154 telling the debugger to ABORT doesn't get you back to the main REPL,
1155 but instead just gives you another stack exhaustion error. The problem
1156 doesn't occur in the trivial case
1157 * (defun frob () (frob) (frob))
1160 but it has happened in more complicated cases (which I haven't
1161 figured out how to reproduce).
1164 (fixed in sbcl-0.7.2.9)
1167 FUNCTION-LAMBDA-EXPRESSION doesn't work right in 0.7.0 or 0.7.2.9:
1168 * (function-lambda-expression #'(lambda (x) x))
1169 debugger invoked on condition of type TYPE-ERROR:
1170 The value NIL is not of type SB-C::DEBUG-SOURCE
1171 (reported by Alexey Dejneka sbcl-devel 2002-04-12)
1174 Functions SUBTYPEP, TYPEP, UPGRADED-ARRAY-ELEMENT-TYPE, and
1175 UPGRADED-COMPLEX-PART-TYPE should have an optional environment argument.
1176 (reported by Alexey Dejneka sbcl-devel 2002-04-12)
1179 Compiling the following code causes SBCL 0.7.2 to bug. This only
1180 happens with optimization enabled, and only when the loop variable is
1181 being incremented by more than 1.
1183 (declare (optimize (safety 0) (space 0) (debug 0) (speed 3)))
1184 (loop for i from 0 to 10 by 2
1185 do (foo (svref array i))) (svref array (1+ i)))
1186 (reported by Eric Marsden sbcl-devel 2002-04-15)
1189 (reported by Robert E. Brown 2002-04-16)
1190 When a function is called with too few arguments, causing the
1191 debugger to be entered, the uninitialized slots in the bad call frame
1192 seem to cause GCish problems, being interpreted as tagged data even
1193 though they're not. In particular, executing ROOM in the
1194 debugger at that point causes AVER failures:
1197 * (lisp-implementation-version)
1203 failed AVER: "(SAP= CURRENT END)"
1204 (Christophe Rhodes reports that this doesn't occur on the SPARC, which
1205 isn't too surprising since there are many differences in stack
1206 implementation and GC conservatism between the X86 and other ports.)
1209 The type system still can't quite deal with all useful identities;
1210 for instance, as of sbcl-0.7.2.18, the type specifier '(and (real -1
1211 7) (real 4 8)) is a HAIRY-TYPE rather than that which would be hoped
1212 for, viz: '(real 4 7).
1215 Array types with element-types of some unknown type are falsely being
1216 assumed to be of type (ARRAY T) by the compiler in some cases. The
1217 following code demonstrates the problem:
1220 (declare (type (vector bar) x))
1222 (deftype bar () 'single-float)
1223 (foo (make-array 3 :element-type 'bar))
1224 -> TYPE-ERROR "The value #(0.0 0.0 0.0) is not of type (VECTOR BAR)."
1225 (typep (make-array 3 :element-type 'bar) '(vector bar))
1228 The easy solution is to make the functions which depend on knowing
1229 the upgraded-array-element-type (in compiler/array-tran and
1230 compiler/generic/vm-tran as of sbcl-0.7.3.x) be slightly smarter about
1231 unknown types; an alternative is to have the
1232 specialized-element-type slot in the ARRAY-TYPE structure be
1233 *WILD-TYPE* for UNKNOWN-TYPE element types.
1237 (in-package :cl-user)
1239 (defmethod permanentize ((uustk uustk))
1240 (flet ((frob (hash-table test-for-deletion)
1242 (obj-entry.stale? (oe)
1243 (destructuring-bind (key . datum) oe
1244 (declare (type simple-vector key))
1245 (deny0 (void? datum))
1246 (some #'stale? key))))
1247 (declare (inline frob obj-entry.stale?))
1248 (frob (uustk.args-hash->obj-alist uustk)
1250 (frob (uustk.hash->memoized-objs-list uustk)
1253 in sbcl-0.7.3.11 causes an assertion failure,
1256 (AND (NULL (BLOCK-SUCC B))
1257 (NOT (BLOCK-DELETE-P B))
1258 (NOT (EQ B (COMPONENT-HEAD #)))))"
1261 In sbcl-0.7.3.11, compiling the (illegal) code
1262 (in-package :cl-user)
1263 (defmethod prove ((uustk uustk))
1264 (zap ((frob () nil))
1266 gives the (not terribly clear) error message
1268 ; (during macroexpansion of (DEFMETHOD PROVE ...))
1269 ; can't get template for (FROB NIL NIL)
1270 The problem seems to be that the code walker used by the DEFMETHOD
1271 macro is unhappy with the illegal syntax in the method body, and
1272 is giving an unclear error message.
1275 (reported by Dan Barlow on sbcl-devel 2002-05-10)
1276 In sbcl-0.7.3.12, doing
1277 (defstruct foo bar baz)
1278 (compile nil (lambda (x) (or x (foo-baz x))))
1280 debugger invoked on condition of type SB-INT:BUG:
1281 full call to SB-KERNEL:%INSTANCE-REF
1282 This is probably a bug in SBCL itself. [...]
1283 Since this is a reasonable user error, it shouldn't be reported as
1287 (reported by Alexey Dejneka on sbcl-devel 2002-05-12)
1290 (declare (special *x*))
1294 ; (DECLARE (SPECIAL *X*))
1297 ; caught STYLE-WARNING:
1298 ; using the lexical binding of the symbol *X*, not the
1299 ; dynamic binding, even though the symbol name follows the usual naming
1300 ; convention (names like *FOO*) for special variables
1301 ; compilation unit finished
1302 ; caught 1 STYLE-WARNING condition
1303 But the code works as it should. Checked in 0.6.12.43 and later.
1306 (reported by Matthias Hoelzl on sbcl-devel 2002-05-13)
1307 * (defmacro foo () ''x)
1316 debugger invoked on condition of type UNDEFINED-FUNCTION:
1317 The function FOO is undefined.
1320 DEFUNCT CATEGORIES OF BUGS
1322 These labels were used for bugs related to the old IR1 interpreter.
1323 The # values reached 6 before the category was closed down.