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 The ANSI spec, in section "22.3.5.2 Tilde Less-Than-Sign: Logical Block",
147 says that an error is signalled if ~W, ~_, ~<...~:>, ~I, or ~:T is used
148 inside "~<..~>" (without the colon modifier on the closing syntax).
149 However, SBCL doesn't do this:
150 * (FORMAT T "~<munge~wegnum~>" 12)
155 Sometimes (SB-EXT:QUIT) fails with
156 Argh! maximum interrupt nesting depth (4096) exceeded, exiting
157 Process inferior-lisp exited abnormally with code 1
158 I haven't noticed a repeatable case of this yet.
161 The printer doesn't report closures very well. This is true in
165 #<Closure Over Function "DEFUN STRUCTURE-SLOT-ACCESSOR" {134D1A1}>
166 It would be nice to make closures have a settable name slot,
167 and make things like DEFSTRUCT and FLET, which create closures,
168 set helpful values into this slot.
171 And as long as we're wishing, it would be awfully nice if INSPECT could
172 also report on closures, telling about the values of the bound variables.
175 The compiler assumes that any time a function of declared FTYPE
176 doesn't signal an error, its arguments were of the declared type.
177 E.g. compiling and loading
178 (DECLAIM (OPTIMIZE (SAFETY 3)))
179 (DEFUN FACTORIAL (X) (GAMMA (1+ X)))
181 (DECLAIM (FTYPE (FUNCTION (UNSIGNED-BYTE)) FACTORIAL))
183 (COND ((> (FACTORIAL X) 1.0E6)
184 (FORMAT T "too big~%"))
186 (FORMAT T "exactly ~S~%" (FACTORIAL X)))
188 (FORMAT T "approximately ~S~%" (FACTORIAL X)))))
191 will cause the INTEGERP case to be selected, giving bogus output a la
193 This violates the "declarations are assertions" principle.
194 According to the ANSI spec, in the section "System Class FUNCTION",
195 this is a case of "lying to the compiler", but the lying is done
196 by the code which calls FACTORIAL with non-UNSIGNED-BYTE arguments,
197 not by the unexpectedly general definition of FACTORIAL. In any case,
198 "declarations are assertions" means that lying to the compiler should
199 cause an error to be signalled, and should not cause a bogus
200 result to be returned. Thus, the compiler should not assume
201 that arbitrary functions check their argument types. (It might
202 make sense to add another flag (CHECKED?) to DEFKNOWN to
203 identify functions which *do* check their argument types.)
204 (Also, verify that the compiler handles declared function
205 return types as assertions.)
208 TYPEP of VALUES types is sometimes implemented very inefficiently, e.g. in
209 (DEFTYPE INDEXOID () '(INTEGER 0 1000))
211 (DECLARE (TYPE INDEXOID X))
212 (THE (VALUES INDEXOID)
214 where the implementation of the type check in function FOO
215 includes a full call to %TYPEP. There are also some fundamental problems
216 with the interpretation of VALUES types (inherited from CMU CL, and
217 from the ANSI CL standard) as discussed on the cmucl-imp@cons.org
218 mailing list, e.g. in Robert Maclachlan's post of 21 Jun 2000.
221 The definitions of SIGCONTEXT-FLOAT-REGISTER and
222 %SET-SIGCONTEXT-FLOAT-REGISTER in x86-vm.lisp say they're not
223 supported on FreeBSD because the floating point state is not saved,
224 but at least as of FreeBSD 4.0, the floating point state *is* saved,
225 so they could be supported after all. Very likely
226 SIGCONTEXT-FLOATING-POINT-MODES could now be supported, too.
229 (as discussed by Douglas Crosher on the cmucl-imp mailing list ca.
230 Aug. 10, 2000): CMUCL currently interprets 'member as '(member); same
231 issue with 'union, 'and, 'or etc. So even though according to the
232 ANSI spec, bare 'MEMBER, 'AND, and 'OR are not legal types, CMUCL
233 (and now SBCL) interpret them as legal types.
236 a slew of floating-point-related errors reported by Peter Van Eynde
238 b: SBCL's value for LEAST-POSITIVE-SHORT-FLOAT is bogus, and
239 should probably be 1.4012985e-45. In SBCL,
240 (/ LEAST-POSITIVE-SHORT-FLOAT 2) returns a number smaller
241 than LEAST-POSITIVE-SHORT-FLOAT. Similar problems
242 exist for LEAST-NEGATIVE-SHORT-FLOAT, LEAST-POSITIVE-LONG-FLOAT,
243 and LEAST-NEGATIVE-LONG-FLOAT.
244 c: Many expressions generate floating infinity on x86/Linux:
249 PVE's regression tests want them to raise errors. sbcl-0.7.0.5
250 on x86/Linux generates the infinities instead. That might or
251 might not be conforming behavior, but it's also inconsistent,
252 which is almost certainly wrong. (Inconsistency: (/ 1 0.0)
253 should give the same result as (/ 1.0 0.0), but instead (/ 1 0.0)
254 generates SINGLE-FLOAT-POSITIVE-INFINITY and (/ 1.0 0.0)
256 d: (in section12.erg) various forms a la
257 (FLOAT 1 DOUBLE-FLOAT-EPSILON)
258 don't give the right behavior.
261 type safety errors reported by Peter Van Eynde July 25, 2000:
262 a: (COERCE (QUOTE (A B C)) (QUOTE (VECTOR * 4)))
264 In general lengths of array type specifications aren't
265 checked by COERCE, so it fails when the spec is
266 (VECTOR 4), (STRING 2), (SIMPLE-BIT-VECTOR 3), or whatever.
267 b: CONCATENATE has the same problem of not checking the length
268 of specified output array types. MAKE-SEQUENCE and MAP and
269 MERGE also have the same problem.
270 c: (COERCE 'AND 'FUNCTION) returns something related to
271 (MACRO-FUNCTION 'AND), but ANSI says it should raise an error.
272 f: (FLOAT-RADIX 2/3) should signal an error instead of
274 g: (LOAD "*.lsp") should signal FILE-ERROR.
275 h: (MAKE-CONCATENATED-STREAM (MAKE-STRING-OUTPUT-STREAM))
276 should signal TYPE-ERROR.
277 i: MAKE-TWO-WAY-STREAM doesn't check that its arguments can
278 be used for input and output as needed. It should fail with
279 TYPE-ERROR when handed e.g. the results of
280 MAKE-STRING-INPUT-STREAM or MAKE-STRING-OUTPUT-STREAM in
281 the inappropriate positions, but doesn't.
282 j: (PARSE-NAMESTRING (COERCE (LIST #\f #\o #\o (CODE-CHAR 0) #\4 #\8)
284 should probably signal an error instead of making a pathname with
286 k: READ-BYTE is supposed to signal TYPE-ERROR when its argument is
287 not a binary input stream, but instead cheerfully reads from
288 character streams, e.g. (MAKE-STRING-INPUT-STREAM "abc").
291 DEFCLASS bugs reported by Peter Van Eynde July 25, 2000:
292 a: (DEFCLASS FOO () (A B A)) should signal a PROGRAM-ERROR, and
294 b: (DEFCLASS FOO () (A B A) (:DEFAULT-INITARGS X A X B)) should
295 signal a PROGRAM-ERROR, and doesn't.
296 c: (DEFCLASS FOO07 NIL ((A :ALLOCATION :CLASS :ALLOCATION :CLASS))),
297 and other DEFCLASS forms with duplicate specifications in their
298 slots, should signal a PROGRAM-ERROR, and doesn't.
299 d: (DEFGENERIC IF (X)) should signal a PROGRAM-ERROR, but instead
300 causes a COMPILER-ERROR.
303 SYMBOL-MACROLET bugs reported by Peter Van Eynde July 25, 2000:
304 a: (SYMBOL-MACROLET ((T TRUE)) ..) should probably signal
305 PROGRAM-ERROR, but SBCL accepts it instead.
306 b: SYMBOL-MACROLET should refuse to bind something which is
307 declared as a global variable, signalling PROGRAM-ERROR.
308 c: SYMBOL-MACROLET should signal PROGRAM-ERROR if something
309 it binds is declared SPECIAL inside.
312 miscellaneous errors reported by Peter Van Eynde July 25, 2000:
314 (DEFGENERIC FOO02 (X))
315 (DEFMETHOD FOO02 ((X NUMBER)) T)
316 (LET ((M (FIND-METHOD (FUNCTION FOO02)
318 (LIST (FIND-CLASS (QUOTE NUMBER))))))
319 (REMOVE-METHOD (FUNCTION FOO02) M)
320 (DEFGENERIC FOO03 (X))
321 (ADD-METHOD (FUNCTION FOO03) M)))
322 should give an error, but SBCL allows it.
323 b: READ should probably return READER-ERROR, not the bare
324 arithmetic error, when input a la "1/0" or "1e1000" causes
328 It has been reported (e.g. by Peter Van Eynde) that there are
329 several metaobject protocol "errors". (In order to fix them, we might
330 need to document exactly what metaobject protocol specification
331 we're following -- the current code is just inherited from PCL.)
334 The implementation of #'+ returns its single argument without
335 type checking, e.g. (+ "illegal") => "illegal".
338 The debugger LIST-LOCATIONS command doesn't work properly.
341 Compiling and loading
342 (DEFUN FAIL (X) (THROW 'FAIL-TAG X))
344 then requesting a BACKTRACE at the debugger prompt gives no information
345 about where in the user program the problem occurred.
348 The compiler is supposed to do type inference well enough that
351 ((SIMPLE-ARRAY SINGLE-FLOAT)
353 (DECLARE (TYPE (SIMPLE-ARRAY SINGLE-FLOAT) X))
356 is redundant. However, as reported by Juan Jose Garcia Ripoll for
357 CMU CL, it sometimes doesn't. Adding declarations is a pretty good
358 workaround for the problem for now, but can't be done by the TYPECASE
359 macros themselves, since it's too hard for the macro to detect
360 assignments to the variable within the clause.
361 Note: The compiler *is* smart enough to do the type inference in
362 many cases. This case, derived from a couple of MACROEXPAND-1
363 calls on Ripoll's original test case,
365 (DECLARE (OPTIMIZE SPEED (SAFETY 0)))
366 (COND ((TYPEP A '(SIMPLE-ARRAY SINGLE-FLOAT)) NIL
367 (LET ((LENGTH (ARRAY-TOTAL-SIZE A)))
368 (LET ((I 0) (G2554 LENGTH))
369 (DECLARE (TYPE REAL G2554) (TYPE REAL I))
372 (WHEN (>= I G2554) (GO SB-LOOP::END-LOOP))
373 (SETF (ROW-MAJOR-AREF A I) (- (ROW-MAJOR-AREF A I)))
374 (GO SB-LOOP::NEXT-LOOP)
375 SB-LOOP::END-LOOP))))))
376 demonstrates the problem; but the problem goes away if the TAGBODY
377 and GO forms are removed (leaving the SETF in ordinary, non-looping
378 code), or if the TAGBODY and GO forms are retained, but the
379 assigned value becomes 0.0 instead of (- (ROW-MAJOR-AREF A I)).
382 Paul Werkowski wrote on cmucl-imp@cons.org 2000-11-15
383 I am looking into this problem that showed up on the cmucl-help
384 list. It seems to me that the "implementation specific environment
385 hacking functions" found in pcl/walker.lisp are completely messed
386 up. The good thing is that they appear to be barely used within
387 PCL and the munged environment object is passed to cmucl only
388 in calls to macroexpand-1, which is probably why this case fails.
389 SBCL uses essentially the same code, so if the environment hacking
390 is screwed up, it affects us too.
393 Using the pretty-printer from the command prompt gives funny
394 results, apparently because the pretty-printer doesn't know
395 about user's command input, including the user's carriage return
396 that the user, and therefore the pretty-printer thinks that
397 the new output block should start indented 2 or more characters
398 rightward of the correct location.
401 (probably related to bug #70; maybe related to bug #109)
402 As reported by Carl Witty on submit@bugs.debian.org 1999-05-08,
404 (in-package "CL-USER")
405 (defun equal-terms (termx termy)
407 ((alpha-equal-bound-term-lists (listx listy)
408 (or (and (null listx) (null listy))
410 (let ((bindings-x (bindings-of-bound-term (car listx)))
411 (bindings-y (bindings-of-bound-term (car listy))))
412 (if (and (null bindings-x) (null bindings-y))
413 (alpha-equal-terms (term-of-bound-term (car listx))
414 (term-of-bound-term (car listy)))
415 (and (= (length bindings-x) (length bindings-y))
417 (enter-binding-pairs (bindings-of-bound-term (car listx))
418 (bindings-of-bound-term (car listy)))
419 (alpha-equal-terms (term-of-bound-term (car listx))
420 (term-of-bound-term (car listy)))
421 (exit-binding-pairs (bindings-of-bound-term (car listx))
422 (bindings-of-bound-term (car listy)))))))
423 (alpha-equal-bound-term-lists (cdr listx) (cdr listy)))))
425 (alpha-equal-terms (termx termy)
426 (if (and (variable-p termx)
428 (equal-bindings (id-of-variable-term termx)
429 (id-of-variable-term termy))
430 (and (equal-operators-p (operator-of-term termx) (operator-of-term termy))
431 (alpha-equal-bound-term-lists (bound-terms-of-term termx)
432 (bound-terms-of-term termy))))))
436 (with-variable-invocation (alpha-equal-terms termx termy))))))
437 causes an assertion failure
438 The assertion (EQ (C::LAMBDA-TAIL-SET C::CALLER)
439 (C::LAMBDA-TAIL-SET (C::LAMBDA-HOME C::CALLEE))) failed.
441 Bob Rogers reports (1999-07-28 on cmucl-imp@cons.org) a smaller test
442 case with the same problem:
443 (defun parse-fssp-alignment ()
444 ;; Given an FSSP alignment file named by the argument . . .
445 (labels ((get-fssp-char ()
449 ;; Stub body, enough to tickle the bug.
450 (list (read-fssp-char)
454 ANSI specifies that the RESULT-TYPE argument of CONCATENATE must be
455 a subtype of SEQUENCE, but CONCATENATE doesn't check this properly:
456 (CONCATENATE 'SIMPLE-ARRAY #(1 2) '(3)) => #(1 2 3)
457 This also leads to funny behavior when derived type specifiers
458 are used, as originally reported by Milan Zamazal for CMU CL (on the
459 Debian bugs mailing list (?) 2000-02-27), then reported by Martin
460 Atzmueller for SBCL (2000-10-01 on sbcl-devel@lists.sourceforge.net):
461 (DEFTYPE FOO () 'SIMPLE-ARRAY)
462 (CONCATENATE 'FOO #(1 2) '(3))
463 => #<ARRAY-TYPE SIMPLE-ARRAY> is a bad type specifier for
465 The derived type specifier FOO should act the same way as the
466 built-in type SIMPLE-ARRAY here, but it doesn't. That problem
467 doesn't seem to exist for sequence types:
468 (DEFTYPE BAR () 'SIMPLE-VECTOR)
469 (CONCATENATE 'BAR #(1 2) '(3)) => #(1 2 3)
472 As reported by Winton Davies on a CMU CL mailing list 2000-01-10,
473 and reported for SBCL by Martin Atzmueller 2000-10-20: (TRACE GETHASH)
474 crashes SBCL. In general tracing anything which is used in the
475 implementation of TRACE is likely to have the same problem.
478 As reported by Daniel Solaz on cmucl-help@cons.org 2000-11-23,
479 SXHASH returns the same value for all non-STRUCTURE-OBJECT instances,
480 notably including all PCL instances. There's a limit to how much
481 SXHASH can do to return unique values for instances, but at least
482 it should probably look at the class name, the way that it does
483 for STRUCTURE-OBJECTs.
486 (probably related to bug #65; maybe related to bug #109)
487 The compiler doesn't like &OPTIONAL arguments in LABELS and FLET
489 (DEFUN FIND-BEFORE (ITEM SEQUENCE &KEY (TEST #'EQL))
490 (LABELS ((FIND-ITEM (OBJ SEQ TEST &OPTIONAL (VAL NIL))
491 (LET ((ITEM (FIRST SEQ)))
494 ((FUNCALL TEST OBJ ITEM)
497 (FIND-ITEM OBJ (REST SEQ) TEST (NCONC VAL `(,ITEM))))))))
498 (FIND-ITEM ITEM SEQUENCE TEST)))
499 from David Young's bug report on cmucl-help@cons.org 30 Nov 2000
500 causes sbcl-0.6.9 to fail with
501 error in function SB-KERNEL:ASSERT-ERROR:
502 The assertion (EQ (SB-C::LAMBDA-TAIL-SET SB-C::CALLER)
503 (SB-C::LAMBDA-TAIL-SET
504 (SB-C::LAMBDA-HOME SB-C::CALLEE))) failed.
507 (DECLAIM (OPTIMIZE ..)) doesn't work. E.g. even after
508 (DECLAIM (OPTIMIZE (SPEED 3))), things are still optimized with
509 the previous SPEED policy. This bug will probably get fixed in
510 0.6.9.x in a general cleanup of optimization policy.
513 (DECLAIM (OPTIMIZE ..)) doesn't work properly inside LOCALLY forms.
516 As reported by Martin Atzmueller on sbcl-devel 26 Dec 2000,
517 ANSI says that WITH-OUTPUT-TO-STRING should have a keyword
518 :ELEMENT-TYPE, but in sbcl-0.6.9 this is not defined for
519 WITH-OUTPUT-TO-STRING.
522 ANSI says in one place that type declarations can be abbreviated even
523 when the type name is not a symbol, e.g.
524 (DECLAIM ((VECTOR T) *FOOVECTOR*))
525 SBCL doesn't support this. But ANSI says in another place that this
526 isn't allowed. So it's not clear this is a bug after all. (See the
527 e-mail on cmucl-help@cons.org on 2001-01-16 and 2001-01-17 from WHN
531 as pointed out by Dan Barlow on sbcl-devel 2000-07-02:
532 The PICK-TEMPORARY-FILE-NAME utility used by LOAD-FOREIGN uses
533 an easily guessable temporary filename in a way which might open
534 applications using LOAD-FOREIGN to hijacking by malicious users
535 on the same machine. Incantations for doing this safely are
536 floating around the net in various "how to write secure programs
537 despite Unix" documents, and it would be good to (1) fix this in
538 LOAD-FOREIGN, and (2) hunt for any other code which uses temporary
539 files and make it share the same new safe logic.
542 Functions are assigned names based on the context in which they're
543 defined. This is less than ideal for the functions which are
544 used to implement CLOS methods. E.g. the output of
545 (DESCRIBE 'PRINT-OBJECT) lists functions like
546 #<FUNCTION "DEF!STRUCT (TRACE-INFO (:MAKE-LOAD-FORM-FUN SB-KERNEL:JUST-DUMP-IT-NORMALLY) (:PRINT-OBJECT #))" {1020E49}>
548 #<FUNCTION "MACROLET ((FORCE-DELAYED-DEF!METHODS NIL #))" {1242871}>
549 It would be better if these functions' names always identified
550 them as methods, and identified their generic functions and
554 RANDOM-INTEGER-EXTRA-BITS=10 may not be large enough for the RANDOM
555 RNG to be high quality near RANDOM-FIXNUM-MAX; it looks as though
556 the mean of the distribution can be systematically O(0.1%) wrong.
557 Just increasing R-I-E-B is probably not a good solution, since
558 it would decrease efficiency more than is probably necessary. Perhaps
559 using some sort of accept/reject method would be better.
562 Internally the compiler sometimes evaluates
563 (sb-kernel:type/= (specifier-type '*) (specifier-type t))
564 (I stumbled across this when I added an
565 (assert (not (eq type1 *wild-type*)))
566 in the NAMED :SIMPLE-= type method.) '* isn't really a type, and
567 in a type context should probably be translated to T, and so it's
568 probably wrong to ask whether it's equal to the T type and then (using
569 the EQ type comparison in the NAMED :SIMPLE-= type method) return NIL.
570 (I haven't tried to investigate this bug enough to guess whether
571 there might be any user-level symptoms.)
574 a latent cross-compilation/bootstrapping bug: The cross-compilation
575 host's CL:CHAR-CODE-LIMIT is used in target code in readtable.lisp
576 and possibly elsewhere. Instead, we should use the target system's
577 CHAR-CODE-LIMIT. This will probably cause problems if we try to
578 bootstrap on a system which uses a different value of CHAR-CODE-LIMIT
582 Inconsistencies between derived and declared VALUES return types for
583 DEFUN aren't checked very well. E.g. the logic which successfully
584 catches problems like
585 (declaim (ftype (function (fixnum) float) foo))
587 (declare (type integer x))
588 (values x)) ; wrong return type, detected, gives warning, good!
590 (declaim (ftype (function (t) (values t t)) bar))
592 (values x)) ; wrong number of return values, no warning, bad!
593 The cause of this is seems to be that (1) the internal function
594 VALUES-TYPES-EQUAL-OR-INTERSECT used to make the check handles its
595 arguments symmetrically, and (2) when the type checking code was
596 written back when when SBCL's code was still CMU CL, the intent
598 (declaim (ftype (function (t) t) bar))
600 (values x x)) ; wrong number of return values; should give warning?
601 not be warned for, because a two-valued return value is considered
602 to be compatible with callers who expects a single value to be
603 returned. That intent is probably not appropriate for modern ANSI
604 Common Lisp, but fixing this might be complicated because of other
605 divergences between auld-style and new-style handling of
606 multiple-VALUES types. (Some issues related to this were discussed
607 on cmucl-imp at some length sometime in 2000.)
610 The facility for dumping a running Lisp image to disk gets confused
611 when run without the PURIFY option, and creates an unnecessarily large
612 core file (apparently representing memory usage up to the previous
613 high-water mark). Moreover, when the file is loaded, it confuses the
614 GC, so that thereafter memory usage can never be reduced below that
618 The TRACE facility can't be used on some kinds of functions.
619 (Basically, the breakpoint facility was incompletely implemented
620 in the X86 port of CMU CL, and hasn't been fixed in SBCL.)
623 In sbcl-0.6.11.41 (and in all earlier SBCL, and in CMU
624 CL), out-of-line structure slot setters are horribly inefficient
625 whenever the type of the slot is declared, because out-of-line
626 structure slot setters are implemented as closures to save space,
627 so the compiler doesn't compile the type test into code, but
628 instead just saves the type in a lexical closure and interprets it
630 A proper solution involves deciding whether it's really worth
631 saving space by implementing structure slot accessors as closures.
632 (If it's not worth it, the problem vanishes automatically. If it
633 is worth it, there are hacks we could use to force type tests to
634 be compiled anyway, and even shared. E.g. we could implement
635 an EQUAL hash table mapping from types to compiled type tests,
636 and save the appropriate compiled type test as part of each lexical
637 closure; or we could make the lexical closures be placeholders
638 which overwrite their old definition as a lexical closure with
639 a new compiled definition the first time that they're called.)
640 As a workaround for the problem, #'(SETF FOO) expressions can
641 be replaced with (EFFICIENT-SETF-FUNCTION FOO), where
642 (defmacro efficient-setf-function (place-function-name)
643 (or #+sbcl (and (sb-impl::info :function :accessor-for place-function-name)
644 ;; a workaround for the problem, encouraging the
645 ;; inline expansion of the structure accessor, so
646 ;; that the compiler can optimize its type test
647 (let ((new-value (gensym "NEW-VALUE-"))
648 (structure-value (gensym "STRUCTURE-VALUE-")))
649 `(lambda (,new-value ,structure-value)
650 (setf (,place-function-name ,structure-value)
652 ;; no problem, can just use the ordinary expansion
653 `(function (setf ,place-function-name))))
656 There's apparently a bug in CEILING optimization which caused
657 Douglas Crosher to patch the CMU CL version. Martin Atzmueller
658 applied the patches to SBCL and they didn't seem to cause problems
659 (as reported sbcl-devel 2001-05-04). However, since the patches
660 modify nontrivial code which was apparently written incorrectly
661 the first time around, until regression tests are written I'm not
662 comfortable merging the patches in the CVS version of SBCL.
665 As reported by Arthur Lemmens sbcl-devel 2001-05-05, ANSI
666 requires that SYMBOL-MACROLET refuse to rebind special variables,
667 but SBCL doesn't do this. (Also as reported by AL in the same
668 message, SBCL depended on this nonconforming behavior to build
669 itself, because of the way that **CURRENT-SEGMENT** was implemented.
670 As of sbcl-0.6.12.x, this dependence on the nonconforming behavior
671 has been fixed, but the nonconforming behavior remains.)
674 (DESCRIBE 'SB-ALIEN:DEF-ALIEN-TYPE) reports the macro argument list
678 in #<PACKAGE "SB-ALIEN">.
679 Macro-function: #<FUNCTION "DEF!MACRO DEF-ALIEN-TYPE" {19F4A39}>
680 Macro arguments: (#:whole-470 #:environment-471)
681 On Sat, May 26, 2001 09:45:57 AM CDT it was compiled from:
682 /usr/stuff/sbcl/src/code/host-alieneval.lisp
683 Created: Monday, March 12, 2001 07:47:43 AM CST
686 (TIME (ROOM T)) reports more than 200 Mbytes consed even for
687 a clean, just-started SBCL system. And it seems to be right:
688 (ROOM T) can bring a small computer to its knees for a *long*
689 time trying to GC afterwards. Surely there's some more economical
690 way to implement (ROOM T).
693 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
695 ;;; This file fails to compile.
696 ;;; Maybe this bug is related to bugs #65, #70 in the BUGS file.
697 (in-package :cl-user)
703 ;; Uncomment and it works
706 In SBCL 0.6.12.42, the problem is
707 internal error, failed AVER:
708 "(COMMON-LISP:EQ (SB!C::LAMBDA-TAIL-SET SB!C::CALLER)
709 (SB!C::LAMBDA-TAIL-SET (SB!C::LAMBDA-HOME SB!C::CALLEE)))"
712 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
714 ;;; The compiler is flushing the argument type test, and the default
715 ;;; case in the cond, so that calling with say a fixnum 0 causes a
717 (declaim (optimize (safety 2) (speed 3)))
719 (declare (type (or string stream) x))
720 (cond ((typep x 'string) 'string)
721 ((typep x 'stream) 'stream)
724 The symptom in sbcl-0.6.12.42 on OpenBSD is actually (TST 0)=>STREAM
725 (not the SIGBUS reported in the comment) but that's broken too;
726 type declarations are supposed to be treated as assertions unless
727 SAFETY 0, so we should be getting a TYPE-ERROR.
730 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
732 (in-package :cl-user)
733 ;;; From: David Gadbois <gadbois@cyc.com>
735 ;;; Logical pathnames aren't externalizable.
737 (let ((tempfile "/tmp/test.lisp"))
738 (setf (logical-pathname-translations "XXX")
739 '(("XXX:**;*.*" "/tmp/**/*.*")))
740 (with-open-file (out tempfile :direction :output)
741 (write-string "(defvar *path* #P\"XXX:XXX;FOO.LISP\")" out))
742 (compile-file tempfile))
743 The error message in sbcl-0.6.12.42 is
745 ; (while making load form for #<SB-IMPL::LOGICAL-HOST "XXX">)
746 ; A logical host can't be dumped as a constant: #<SB-IMPL::LOGICAL-HOST "XXX">
749 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
751 (in-package :cl-user)
752 ;;; The following invokes a compiler error.
753 (declaim (optimize (speed 2) (debug 3)))
756 (unwind-protect nil)))
760 The error message in sbcl-0.6.12.42 is
761 internal error, failed AVER:
762 "(COMMON-LISP:EQ (SB!C::TN-ENVIRONMENT SB!C:TN) SB!C::TN-ENV)"
765 When the compiler inline expands functions, it may be that different
766 kinds of return values are generated from different code branches.
767 E.g. an inline expansion of POSITION generates integer results
768 from one branch, and NIL results from another. When that inline
769 expansion is used in a context where only one of those results
772 (aref *a1* (position x *a2*)))
773 and the compiler can't prove that the unacceptable branch is
774 never taken, then bogus type mismatch warnings can be generated.
775 If you need to suppress the type mismatch warnings, you can
776 suppress the inline expansion,
778 #+sbcl (declare (notinline position)) ; to suppress bug 117 bogowarnings
779 (aref *a1* (position x *a2*)))
780 or, sometimes, suppress them by declaring the result to be of an
783 (aref *a1* (the integer (position x *a2*))))
785 This is not a new compiler problem in 0.7.0, but the new compiler
786 transforms for FIND, POSITION, FIND-IF, and POSITION-IF make it
787 more conspicuous. If you don't need performance from these functions,
788 and the bogus warnings are a nuisance for you, you can return to
789 your pre-0.7.0 state of grace with
790 #+sbcl (declaim (notinline find position find-if position-if)) ; bug 117..
793 as reported by Eric Marsden on cmucl-imp@cons.org 2001-08-14:
794 (= (FLOAT 1 DOUBLE-FLOAT-EPSILON)
795 (+ (FLOAT 1 DOUBLE-FLOAT-EPSILON) DOUBLE-FLOAT-EPSILON)) => T
796 when of course it should be NIL. (He says it only fails for X86,
797 not SPARC; dunno about Alpha.)
799 Also, "the same problem exists for LONG-FLOAT-EPSILON,
800 DOUBLE-FLOAT-NEGATIVE-EPSILON, LONG-FLOAT-NEGATIVE-EPSILON (though
801 for the -negative- the + is replaced by a - in the test)."
803 Raymond Toy comments that this is tricky on the X86 since its FPU
804 uses 80-bit precision internally.
807 The compiler incorrectly figures the return type of
808 (DEFUN FOO (FRAME UP-FRAME)
815 This problem exists in CMU CL 18c too. When I reported it on
816 cmucl-imp@cons.org, Raymond Toy replied 23 Aug 2001 with
817 a partial explanation, but no fix has been found yet.
820 Even in sbcl-0.pre7.x, which is supposed to be free of the old
821 non-ANSI behavior of treating the function return type inferred
822 from the current function definition as a declaration of the
823 return type from any function of that name, the return type of NIL
824 is attached to FOO in 120a above, and used to optimize code which
828 There was some sort of screwup in handling of
829 (IF (NOT (IGNORE-ERRORS ..))). E.g.
831 (if (not (ignore-errors
832 (make-pathname :host "foo" :directory "!bla" :name "bar")))
834 (error "notunlessnot")))
835 The (NOT (IGNORE-ERRORS ..)) form evaluates to T, so this should be
836 printing "ok", but instead it's going to the ERROR. This problem
837 seems to've been introduced by MNA's HANDLER-CASE patch (sbcl-devel
838 2001-07-17) and as a workaround (put in sbcl-0.pre7.14.flaky4.12)
839 I reverted back to the old weird HANDLER-CASE code. However, I
840 think the problem looks like a compiler bug in handling RETURN-FROM,
841 so I left the MNA-patched code in HANDLER-CASE (suppressed with
842 #+NIL) and I'd like to go back to see whether this really is
843 a compiler bug before I delete this BUGS entry.
846 The *USE-IMPLEMENTATION-TYPES* hack causes bugs, particularly
847 (IN-PACKAGE :SB-KERNEL)
848 (TYPE= (SPECIFIER-TYPE '(VECTOR T))
849 (SPECIFIER-TYPE '(VECTOR UNDEFTYPE)))
850 Then because of this, the compiler bogusly optimizes
851 (TYPEP #(11) '(SIMPLE-ARRAY UNDEF-TYPE 1))
852 to T. Unfortunately, just setting *USE-IMPLEMENTATION-TYPES* to
853 NIL around sbcl-0.pre7.14.flaky4.12 didn't work: the compiler complained
854 about type mismatches (probably harmlessly, another instance of bug 117);
855 and then cold init died with a segmentation fault.
858 As of version 0.pre7.14, SBCL's implementation of MACROLET makes
859 the entire lexical environment at the point of MACROLET available
860 in the bodies of the macroexpander functions. In particular, it
861 allows the function bodies (which run at compile time) to try to
862 access lexical variables (which are only defined at runtime).
863 It doesn't even issue a warning, which is bad.
865 The SBCL behavior arguably conforms to the ANSI spec (since the
866 spec says that the behavior is undefined, ergo anything conforms).
867 However, it would be better to issue a compile-time error.
868 Unfortunately I (WHN) don't see any simple way to detect this
869 condition in order to issue such an error, so for the meantime
870 SBCL just does this weird broken "conforming" thing.
872 The ANSI standard says, in the definition of the special operator
874 The macro-expansion functions defined by MACROLET are defined
875 in the lexical environment in which the MACROLET form appears.
876 Declarations and MACROLET and SYMBOL-MACROLET definitions affect
877 the local macro definitions in a MACROLET, but the consequences
878 are undefined if the local macro definitions reference any
879 local variable or function bindings that are visible in that
881 Then it seems to contradict itself by giving the example
883 (macrolet ((fudge (z)
884 ;The parameters x and flag are not accessible
885 ; at this point; a reference to flag would be to
886 ; the global variable of that name.
887 ` (if flag (* ,z ,z) ,z)))
888 ;The parameters x and flag are accessible here.
892 The comment "a reference to flag would be to the global variable
893 of the same name" sounds like good behavior for the system to have.
894 but actual specification quoted above says that the actual behavior
898 (as reported by Gabe Garza on cmucl-help 2001-09-21)
900 (defun test-pred (x y)
904 (func (lambda () x)))
905 (print (eq func func))
906 (print (test-pred func func))
907 (delete func (list func))))
908 Now calling (TEST-CASE) gives output
911 (#<FUNCTION {500A9EF9}>)
912 Evidently Python thinks of the lambda as a code transformation so
913 much that it forgets that it's also an object.
919 The DEFSTRUCT section of the ANSI spec, in the :CONC-NAME section,
920 specifies a precedence rule for name collisions between slot accessors of
921 structure classes related by inheritance. As of 0.7.0, SBCL still
925 insufficient syntax checking in MACROLET:
927 (macrolet ((defmacro bar (z) `(+ z z)))
929 shouldn't compile without error (because of the extra DEFMACRO symbol).
932 As of sbcl-0.pre7.86.flaky7.3, the cross-compiler, and probably
933 the CL:COMPILE function (which is based on the same %COMPILE
934 mechanism) get confused by
936 (labels ((sxhash-number (x)
938 (fixnum (sxhash x)) ; through DEFTRANSFORM
939 (integer (sb!bignum:sxhash-bignum x))
940 (single-float (sxhash x)) ; through DEFTRANSFORM
941 (double-float (sxhash x)) ; through DEFTRANSFORM
942 #!+long-float (long-float (error "stub: no LONG-FLOAT"))
943 (ratio (let ((result 127810327))
944 (declare (type fixnum result))
945 (mixf result (sxhash-number (numerator x)))
946 (mixf result (sxhash-number (denominator x)))
948 (complex (let ((result 535698211))
949 (declare (type fixnum result))
950 (mixf result (sxhash-number (realpart x)))
951 (mixf result (sxhash-number (imagpart x)))
953 (sxhash-recurse (x &optional (depthoid +max-hash-depthoid+))
954 (declare (type index depthoid))
958 (mix (sxhash-recurse (car x) (1- depthoid))
959 (sxhash-recurse (cdr x) (1- depthoid)))
962 (if (typep x 'structure-object)
964 (sxhash ; through DEFTRANSFORM
965 (class-name (layout-class (%instance-layout x)))))
967 (symbol (sxhash x)) ; through DEFTRANSFORM
968 (number (sxhash-number x))
971 (simple-string (sxhash x)) ; through DEFTRANSFORM
972 (string (%sxhash-substring x))
973 (bit-vector (let ((result 410823708))
974 (declare (type fixnum result))
975 (dotimes (i (min depthoid (length x)))
976 (mixf result (aref x i)))
978 (t (logxor 191020317 (sxhash (array-rank x))))))
981 (sxhash (char-code x)))) ; through DEFTRANSFORM
984 complaining "function called with two arguments, but wants exactly
985 one" about SXHASH-RECURSE. (This might not be strictly a new bug,
986 since IIRC post-fork CMU CL has also had problems with &OPTIONAL
987 arguments in FLET/LABELS: it might be an old Python bug which is
988 only exercised by the new arrangement of the SBCL compiler.)
991 Ideally, uninterning a symbol would allow it, and its associated
992 FDEFINITION and PROCLAIM data, to be reclaimed by the GC. However,
993 at least as of sbcl-0.7.0, this isn't the case. Information about
994 FDEFINITIONs and PROCLAIMed properties is stored in globaldb.lisp
995 essentially in ordinary (non-weak) hash tables keyed by symbols.
996 Thus, once a system has an entry in this system, it tends to live
997 forever, even when it is uninterned and all other references to it
1001 (reported by Arnaud Rouanet on cmucl-imp 2001-12-18)
1002 (defmethod foo ((x integer))
1004 (defmethod foo :around ((x integer))
1006 (call-next-method)))
1007 Now (FOO 3) should return 3, but instead it returns 4.
1010 (SB-DEBUG:BACKTRACE) output should start with something
1011 including the name BACKTRACE, not (as in 0.pre7.88)
1012 just "0: (\"hairy arg processor\" ...)". Until about
1013 sbcl-0.pre7.109, the names in BACKTRACE were all screwed
1014 up compared to the nice useful names in sbcl-0.6.13.
1015 Around sbcl-0.pre7.109, they were mostly fixed by using
1016 NAMED-LAMBDA to implement DEFUN. However, there are still
1017 some screwups left, e.g. as of sbcl-0.pre7.109, there are
1018 still some functions named "hairy arg processor" and
1019 "SB-INT:&MORE processor".
1022 (reported by Alexey Dejneka sbcl-devel 2002-01-03)
1024 SUBTYPEP does not work well with redefined classes:
1026 * (defclass a () ())
1028 * (defclass b () ())
1033 * (defclass b (a) ())
1038 * (defclass b () ())
1046 This is probably due to underzealous clearing of the type caches; a
1047 brute-force solution in that case would be to make a defclass expand
1048 into something that included a call to SB-KERNEL::CLEAR-TYPE-CACHES,
1049 but there may be a better solution.
1052 Pretty-printing nested backquotes doesn't work right, as
1053 reported by Alexey Dejneka sbcl-devel 2002-01-13:
1055 ``(FOO SB-IMPL::BACKQ-COMMA-AT S)
1056 * (lisp-implementation-version)
1060 (as reported by Lynn Quam on cmucl-imp ca. 2002-01-16)
1061 %NATURALIZE-C-STRING conses a lot, like 16 bytes per byte
1062 of the naturalized string. We could probably port the patches
1063 from the cmucl-imp mailing list.
1066 (reported by Jesse Bouwman 2001-10-24 through the unfortunately
1067 prominent SourceForge web/db bug tracking system, which is
1068 unfortunately not a reliable way to get a timely response from
1069 the SBCL maintainers)
1070 In the course of trying to build a test case for an
1071 application error, I encountered this behavior:
1072 If you start up sbcl, and then lay on CTRL-C for a
1073 minute or two, the lisp process will eventually say:
1074 %PRIMITIVE HALT called; the party is over.
1075 and throw you into the monitor. If I start up lisp,
1076 attach to the process with strace, and then do the same
1077 (abusive) thing, I get instead:
1078 access failure in heap page not marked as write-protected
1079 and the monitor again. I don't know enough to have the
1080 faintest idea of what is going on here.
1081 This is with sbcl 6.12, uname -a reports:
1082 Linux prep 2.2.19 #4 SMP Tue Apr 24 13:59:52 CDT 2001 i686 unknown
1083 I (WHN) have verified that the same thing occurs on sbcl-0.pre7.141
1084 under OpenBSD 2.9 on my X86 laptop. Do be patient when you try it:
1085 it took more than two minutes (but less than five) for me.
1088 (This was once known as IR1-4, but it lived on even after the
1089 IR1 interpreter went to the big bit bucket in the sky.)
1090 The system accepts DECLAIM in most places where DECLARE would be
1091 accepted, without even issuing a warning. ANSI allows this, but since
1092 it's fairly easy to mistype DECLAIM instead of DECLARE, and the
1093 meaning is rather different, and it's unlikely that the user
1094 has a good reason for doing DECLAIM not at top level, it would be
1095 good to issue a STYLE-WARNING when this happens. A possible
1096 fix would be to issue STYLE-WARNINGs for DECLAIMs not at top level,
1097 or perhaps to issue STYLE-WARNINGs for any EVAL-WHEN not at top level.
1098 [This is considered an IR1-interpreter-related bug because until
1099 EVAL-WHEN is rewritten, which won't happen until after the IR1
1100 interpreter is gone, the system's notion of what's a top-level form
1101 and what's not will remain too confused to fix this problem.]
1104 ANSI allows types `(COMPLEX ,FOO) to use very hairy values for
1105 FOO, e.g. (COMPLEX (AND REAL (SATISFIES ODDP))). The old CMU CL
1106 COMPLEX implementation didn't deal with this, and hasn't been
1107 upgraded to do so. (This doesn't seem to be a high priority
1108 conformance problem, since seems hard to construct useful code
1112 Floating point errors are reported poorly. E.g. on x86 OpenBSD
1115 debugger invoked on condition of type SB-KERNEL:FLOATING-POINT-EXCEPTION:
1116 An arithmetic error SB-KERNEL:FLOATING-POINT-EXCEPTION was signalled.
1117 No traps are enabled? How can this be?
1118 It should be possible to be much more specific (overflow, division
1119 by zero, etc.) and of course the "How can this be?" should be fixable.
1122 In sbcl-0.7.1.3 on x86, COMPILE-FILE on the file
1123 (in-package :cl-user)
1126 (defstruct foo bar bletch)
1128 (labels ((kidify1 (kid)
1133 (m+ (frobnicate kid)
1136 (declare (inline kid-frob))
1139 (the simple-vector (foo-bar perd)))))
1141 debugger invoked on condition of type TYPE-ERROR:
1142 The value NIL is not of type SB-C::NODE.
1143 The location of this failure has moved around as various related
1144 issues were cleaned up. As of sbcl-0.7.1.9, it occurs in
1145 NODE-BLOCK called by LAMBDA-COMPONENT called by IR2-CONVERT-CLOSURE.
1148 (essentially the same problem as a CMU CL bug reported by Martin
1149 Cracauer on cmucl-imp 2002-02-19)
1150 There is a hole in structure slot type checking. Compiling and LOADing
1151 (declaim (optimize safety))
1153 (bla 0 :type fixnum))
1155 (let ((foo (make-foo)))
1156 (setf (foo-bla foo) '(1 . 1))
1157 (format t "Is ~a of type ~a a cons? => ~a~%"
1159 (type-of (foo-bla foo))
1160 (consp (foo-bla foo)))))
1162 should signal an error, but in sbcl-0.7.1.21 instead gives the output
1163 Is (1 . 1) of type CONS a cons? => NIL
1164 without signalling an error.
1167 There's some sort of problem with aborting back out of the debugger
1168 after a %DETECT-STACK-EXHAUSTION error in sbcl-0.7.1.38. In some cases
1169 telling the debugger to ABORT doesn't get you back to the main REPL,
1170 but instead just gives you another stack exhaustion error. The problem
1171 doesn't occur in the trivial case
1172 * (defun frob () (frob) (frob))
1175 but it has happened in more complicated cases (which I haven't
1176 figured out how to reproduce).
1179 (fixed in sbcl-0.7.2.9)
1182 FUNCTION-LAMBDA-EXPRESSION doesn't work right in 0.7.0 or 0.7.2.9:
1183 * (function-lambda-expression #'(lambda (x) x))
1184 debugger invoked on condition of type TYPE-ERROR:
1185 The value NIL is not of type SB-C::DEBUG-SOURCE
1186 (reported by Alexey Dejneka sbcl-devel 2002-04-12)
1189 Functions SUBTYPEP, TYPEP, UPGRADED-ARRAY-ELEMENT-TYPE, and
1190 UPGRADED-COMPLEX-PART-TYPE should have an optional environment argument.
1191 (reported by Alexey Dejneka sbcl-devel 2002-04-12)
1194 Compiling the following code causes SBCL 0.7.2 to bug. This only
1195 happens with optimization enabled, and only when the loop variable is
1196 being incremented by more than 1.
1198 (declare (optimize (safety 0) (space 0) (debug 0) (speed 3)))
1199 (loop for i from 0 to 10 by 2
1200 do (foo (svref array i))) (svref array (1+ i)))
1201 (reported by Eric Marsden sbcl-devel 2002-04-15)
1204 (reported by Robert E. Brown 2002-04-16)
1205 When a function is called with too few arguments, causing the
1206 debugger to be entered, the uninitialized slots in the bad call frame
1207 seem to cause GCish problems, being interpreted as tagged data even
1208 though they're not. In particular, executing ROOM in the
1209 debugger at that point causes AVER failures:
1212 * (lisp-implementation-version)
1218 failed AVER: "(SAP= CURRENT END)"
1219 (Christophe Rhodes reports that this doesn't occur on the SPARC, which
1220 isn't too surprising since there are many differences in stack
1221 implementation and GC conservatism between the X86 and other ports.)
1224 HOST-NAMESTRING on a Unix pathname returns "Unix", which isn't
1225 treated as a valid host by anything else in the system. (Reported by
1226 Erik Naggum on comp.lang.lisp 2002-04-18)
1229 The type system still can't quite deal with all useful identities;
1230 for instance, as of sbcl-0.7.2.18, the type specifier '(and (real -1
1231 7) (real 4 8)) is a HAIRY-TYPE rather than that which would be hoped
1232 for, viz: '(real 4 7).
1235 Array types with element-types of some unknown type are falsely being
1236 assumed to be of type (ARRAY T) by the compiler in some cases. The
1237 following code demonstrates the problem:
1240 (declare (type (vector bar) x))
1242 (deftype bar () 'single-float)
1243 (foo (make-array 3 :element-type 'bar))
1244 -> TYPE-ERROR "The value #(0.0 0.0 0.0) is not of type (VECTOR BAR)."
1245 (typep (make-array 3 :element-type 'bar) '(vector bar))
1248 The easy solution is to make the functions which depend on knowing
1249 the upgraded-array-element-type (in compiler/array-tran and
1250 compiler/generic/vm-tran as of sbcl-0.7.3.x) be slightly smarter about
1251 unknown types; an alternative is to have the
1252 specialized-element-type slot in the ARRAY-TYPE structure be
1253 *WILD-TYPE* for UNKNOWN-TYPE element types.
1255 DEFUNCT CATEGORIES OF BUGS
1257 These labels were used for bugs related to the old IR1 interpreter.
1258 The # values reached 6 before the category was closed down.