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 DTC's recommended workaround from the mailing list 3 Mar 2000:
141 (setf (pcl::find-class 'ccc1) (pcl::find-class 'ccc))
144 The ANSI spec, in section "22.3.5.2 Tilde Less-Than-Sign: Logical Block",
145 says that an error is signalled if ~W, ~_, ~<...~:>, ~I, or ~:T is used
146 inside "~<..~>" (without the colon modifier on the closing syntax).
147 However, SBCL doesn't do this:
148 * (FORMAT T "~<munge~wegnum~>" 12)
153 Sometimes (SB-EXT:QUIT) fails with
154 Argh! maximum interrupt nesting depth (4096) exceeded, exiting
155 Process inferior-lisp exited abnormally with code 1
156 I haven't noticed a repeatable case of this yet.
159 In some cases the compiler believes type declarations on array
160 elements without checking them, e.g.
161 (DECLAIM (OPTIMIZE (SAFETY 3) (SPEED 1) (SPACE 1)))
164 (DECLARE (TYPE (SIMPLE-ARRAY CONS 1) X))
165 (WHEN (CONSP (AREF X 0))
167 (BAR (VECTOR (MAKE-FOO :A 11 :B 12)))
170 in SBCL 0.6.5 (and also in CMU CL 18b). This does not happen for
171 all cases, e.g. the type assumption *is* checked if the array
172 elements are declared to be of some structure type instead of CONS.
175 The printer doesn't report closures very well. This is true in
179 #<Closure Over Function "DEFUN STRUCTURE-SLOT-ACCESSOR" {134D1A1}>
180 It would be nice to make closures have a settable name slot,
181 and make things like DEFSTRUCT and FLET, which create closures,
182 set helpful values into this slot.
185 And as long as we're wishing, it would be awfully nice if INSPECT could
186 also report on closures, telling about the values of the bound variables.
189 The compiler assumes that any time a function of declared FTYPE
190 doesn't signal an error, its arguments were of the declared type.
191 E.g. compiling and loading
192 (DECLAIM (OPTIMIZE (SAFETY 3)))
193 (DEFUN FACTORIAL (X) (GAMMA (1+ X)))
195 (DECLAIM (FTYPE (FUNCTION (UNSIGNED-BYTE)) FACTORIAL))
197 (COND ((> (FACTORIAL X) 1.0E6)
198 (FORMAT T "too big~%"))
200 (FORMAT T "exactly ~S~%" (FACTORIAL X)))
202 (FORMAT T "approximately ~S~%" (FACTORIAL X)))))
205 will cause the INTEGERP case to be selected, giving bogus output a la
207 This violates the "declarations are assertions" principle.
208 According to the ANSI spec, in the section "System Class FUNCTION",
209 this is a case of "lying to the compiler", but the lying is done
210 by the code which calls FACTORIAL with non-UNSIGNED-BYTE arguments,
211 not by the unexpectedly general definition of FACTORIAL. In any case,
212 "declarations are assertions" means that lying to the compiler should
213 cause an error to be signalled, and should not cause a bogus
214 result to be returned. Thus, the compiler should not assume
215 that arbitrary functions check their argument types. (It might
216 make sense to add another flag (CHECKED?) to DEFKNOWN to
217 identify functions which *do* check their argument types.)
218 (Also, verify that the compiler handles declared function
219 return types as assertions.)
222 TYPEP of VALUES types is sometimes implemented very inefficiently, e.g. in
223 (DEFTYPE INDEXOID () '(INTEGER 0 1000))
225 (DECLARE (TYPE INDEXOID X))
226 (THE (VALUES INDEXOID)
228 where the implementation of the type check in function FOO
229 includes a full call to %TYPEP. There are also some fundamental problems
230 with the interpretation of VALUES types (inherited from CMU CL, and
231 from the ANSI CL standard) as discussed on the cmucl-imp@cons.org
232 mailing list, e.g. in Robert Maclachlan's post of 21 Jun 2000.
235 The definitions of SIGCONTEXT-FLOAT-REGISTER and
236 %SET-SIGCONTEXT-FLOAT-REGISTER in x86-vm.lisp say they're not
237 supported on FreeBSD because the floating point state is not saved,
238 but at least as of FreeBSD 4.0, the floating point state *is* saved,
239 so they could be supported after all. Very likely
240 SIGCONTEXT-FLOATING-POINT-MODES could now be supported, too.
243 (as discussed by Douglas Crosher on the cmucl-imp mailing list ca.
244 Aug. 10, 2000): CMUCL currently interprets 'member as '(member); same
245 issue with 'union, 'and, 'or etc. So even though according to the
246 ANSI spec, bare 'MEMBER, 'AND, and 'OR are not legal types, CMUCL
247 (and now SBCL) interpret them as legal types.
250 ANSI specifies DEFINE-SYMBOL-MACRO, but it's not defined in SBCL.
251 CMU CL added it ca. Aug 13, 2000, after some discussion on the mailing
252 list, and it is probably possible to use substantially the same
253 patches to add it to SBCL.
256 a slew of floating-point-related errors reported by Peter Van Eynde
258 a: (fixed in sbcl-0.6.11.25)
259 b: SBCL's value for LEAST-POSITIVE-SHORT-FLOAT is bogus, and
260 should probably be 1.4012985e-45. In SBCL,
261 (/ LEAST-POSITIVE-SHORT-FLOAT 2) returns a number smaller
262 than LEAST-POSITIVE-SHORT-FLOAT. Similar problems
263 exist for LEAST-NEGATIVE-SHORT-FLOAT, LEAST-POSITIVE-LONG-FLOAT,
264 and LEAST-NEGATIVE-LONG-FLOAT.
265 c: Many expressions generate floating infinity:
270 PVE's regression tests want them to raise errors. SBCL
271 generates the infinities instead, which may or may not be
273 d: (in section12.erg) various forms a la
274 (FLOAT 1 DOUBLE-FLOAT-EPSILON)
275 don't give the right behavior.
278 type safety errors reported by Peter Van Eynde July 25, 2000:
279 a: (COERCE (QUOTE (A B C)) (QUOTE (VECTOR * 4)))
281 In general lengths of array type specifications aren't
282 checked by COERCE, so it fails when the spec is
283 (VECTOR 4), (STRING 2), (SIMPLE-BIT-VECTOR 3), or whatever.
284 b: CONCATENATE has the same problem of not checking the length
285 of specified output array types. MAKE-SEQUENCE and MAP and
286 MERGE also have the same problem.
287 c: (COERCE 'AND 'FUNCTION) returns something related to
288 (MACRO-FUNCTION 'AND), but ANSI says it should raise an error.
289 f: (FLOAT-RADIX 2/3) should signal an error instead of
291 g: (LOAD "*.lsp") should signal FILE-ERROR.
292 h: (MAKE-CONCATENATED-STREAM (MAKE-STRING-OUTPUT-STREAM))
293 should signal TYPE-ERROR.
294 i: MAKE-TWO-WAY-STREAM doesn't check that its arguments can
295 be used for input and output as needed. It should fail with
296 TYPE-ERROR when handed e.g. the results of
297 MAKE-STRING-INPUT-STREAM or MAKE-STRING-OUTPUT-STREAM in
298 the inappropriate positions, but doesn't.
299 j: (PARSE-NAMESTRING (COERCE (LIST #\f #\o #\o (CODE-CHAR 0) #\4 #\8)
301 should probably signal an error instead of making a pathname with
303 k: READ-BYTE is supposed to signal TYPE-ERROR when its argument is
304 not a binary input stream, but instead cheerfully reads from
305 character streams, e.g. (MAKE-STRING-INPUT-STREAM "abc").
308 DEFCLASS bugs reported by Peter Van Eynde July 25, 2000:
309 a: (DEFCLASS FOO () (A B A)) should signal a PROGRAM-ERROR, and
311 b: (DEFCLASS FOO () (A B A) (:DEFAULT-INITARGS X A X B)) should
312 signal a PROGRAM-ERROR, and doesn't.
313 c: (DEFCLASS FOO07 NIL ((A :ALLOCATION :CLASS :ALLOCATION :CLASS))),
314 and other DEFCLASS forms with duplicate specifications in their
315 slots, should signal a PROGRAM-ERROR, and doesn't.
316 d: (DEFGENERIC IF (X)) should signal a PROGRAM-ERROR, but instead
317 causes a COMPILER-ERROR.
320 SYMBOL-MACROLET bugs reported by Peter Van Eynde July 25, 2000:
321 a: (SYMBOL-MACROLET ((T TRUE)) ..) should probably signal
322 PROGRAM-ERROR, but SBCL accepts it instead.
323 b: SYMBOL-MACROLET should refuse to bind something which is
324 declared as a global variable, signalling PROGRAM-ERROR.
325 c: SYMBOL-MACROLET should signal PROGRAM-ERROR if something
326 it binds is declared SPECIAL inside.
329 type system errors reported by Peter Van Eynde July 25, 2000:
330 c: (SUBTYPEP '(INTEGER (0) (0)) 'NIL) dies with nested errors.
331 d: In general, the system doesn't like '(INTEGER (0) (0)) -- it
332 blows up at the level of SPECIFIER-TYPE with
333 "Lower bound (0) is greater than upper bound (0)." Probably
334 SPECIFIER-TYPE should return NIL instead.
335 g: The type system isn't all that smart about relationships
336 between hairy types, as shown in the type.erg test results,
337 e.g. (SUBTYPEP 'CONS '(NOT ATOM)) => NIL, NIL.
340 miscellaneous errors reported by Peter Van Eynde July 25, 2000:
342 (DEFGENERIC FOO02 (X))
343 (DEFMETHOD FOO02 ((X NUMBER)) T)
344 (LET ((M (FIND-METHOD (FUNCTION FOO02)
346 (LIST (FIND-CLASS (QUOTE NUMBER))))))
347 (REMOVE-METHOD (FUNCTION FOO02) M)
348 (DEFGENERIC FOO03 (X))
349 (ADD-METHOD (FUNCTION FOO03) M)))
350 should give an error, but SBCL allows it.
351 b: READ should probably return READER-ERROR, not the bare
352 arithmetic error, when input a la "1/0" or "1e1000" causes
356 It has been reported (e.g. by Peter Van Eynde) that there are
357 several metaobject protocol "errors". (In order to fix them, we might
358 need to document exactly what metaobject protocol specification
359 we're following -- the current code is just inherited from PCL.)
362 The implementation of #'+ returns its single argument without
363 type checking, e.g. (+ "illegal") => "illegal".
366 Attempting to use COMPILE on something defined by DEFMACRO fails:
367 (DEFMACRO FOO (X) (CONS X X))
369 Error in function C::GET-LAMBDA-TO-COMPILE:
370 #<Closure Over Function "DEFUN (SETF MACRO-FUNCTION)" {480E21B1}> was defined in a non-null environment.
373 (SUBTYPEP '(AND ZILCH INTEGER) 'ZILCH) => NIL, NIL
374 Note: I looked into fixing this in 0.6.11.15, but gave up. The
375 problem seems to be that there are two relevant type methods for
376 the subtypep operation, HAIRY :COMPLEX-SUBTYPEP-ARG2 and
377 INTERSECTION :COMPLEX-SUBTYPEP-ARG1, and only the first is
378 called. This could be fixed, but type dispatch is messy and
379 confusing enough already, I don't want to complicate it further.
380 Perhaps someday we can make CLOS cross-compiled (instead of compiled
381 after bootstrapping) so that we don't need to have the type system
382 available before CLOS, and then we can rewrite the type methods to
383 CLOS methods, and then expressing the solutions to stuff like this
384 should become much more straightforward. -- WHN 2001-03-14
387 The debugger LIST-LOCATIONS command doesn't work properly.
390 Compiling and loading
391 (DEFUN FAIL (X) (THROW 'FAIL-TAG X))
393 then requesting a BACKTRACE at the debugger prompt gives no information
394 about where in the user program the problem occurred.
397 The compiler is supposed to do type inference well enough that
400 ((SIMPLE-ARRAY SINGLE-FLOAT)
402 (DECLARE (TYPE (SIMPLE-ARRAY SINGLE-FLOAT) X))
405 is redundant. However, as reported by Juan Jose Garcia Ripoll for
406 CMU CL, it sometimes doesn't. Adding declarations is a pretty good
407 workaround for the problem for now, but can't be done by the TYPECASE
408 macros themselves, since it's too hard for the macro to detect
409 assignments to the variable within the clause.
410 Note: The compiler *is* smart enough to do the type inference in
411 many cases. This case, derived from a couple of MACROEXPAND-1
412 calls on Ripoll's original test case,
414 (DECLARE (OPTIMIZE SPEED (SAFETY 0)))
415 (COND ((TYPEP A '(SIMPLE-ARRAY SINGLE-FLOAT)) NIL
416 (LET ((LENGTH (ARRAY-TOTAL-SIZE A)))
417 (LET ((I 0) (G2554 LENGTH))
418 (DECLARE (TYPE REAL G2554) (TYPE REAL I))
421 (WHEN (>= I G2554) (GO SB-LOOP::END-LOOP))
422 (SETF (ROW-MAJOR-AREF A I) (- (ROW-MAJOR-AREF A I)))
423 (GO SB-LOOP::NEXT-LOOP)
424 SB-LOOP::END-LOOP))))))
425 demonstrates the problem; but the problem goes away if the TAGBODY
426 and GO forms are removed (leaving the SETF in ordinary, non-looping
427 code), or if the TAGBODY and GO forms are retained, but the
428 assigned value becomes 0.0 instead of (- (ROW-MAJOR-AREF A I)).
431 Paul Werkowski wrote on cmucl-imp@cons.org 2000-11-15
432 I am looking into this problem that showed up on the cmucl-help
433 list. It seems to me that the "implementation specific environment
434 hacking functions" found in pcl/walker.lisp are completely messed
435 up. The good thing is that they appear to be barely used within
436 PCL and the munged environment object is passed to cmucl only
437 in calls to macroexpand-1, which is probably why this case fails.
438 SBCL uses essentially the same code, so if the environment hacking
439 is screwed up, it affects us too.
442 Using the pretty-printer from the command prompt gives funny
443 results, apparently because the pretty-printer doesn't know
444 about user's command input, including the user's carriage return
445 that the user, and therefore the pretty-printer thinks that
446 the new output block should start indented 2 or more characters
447 rightward of the correct location.
450 (probably related to bug #70; maybe related to bug #109)
451 As reported by Carl Witty on submit@bugs.debian.org 1999-05-08,
453 (in-package "CL-USER")
454 (defun equal-terms (termx termy)
456 ((alpha-equal-bound-term-lists (listx listy)
457 (or (and (null listx) (null listy))
459 (let ((bindings-x (bindings-of-bound-term (car listx)))
460 (bindings-y (bindings-of-bound-term (car listy))))
461 (if (and (null bindings-x) (null bindings-y))
462 (alpha-equal-terms (term-of-bound-term (car listx))
463 (term-of-bound-term (car listy)))
464 (and (= (length bindings-x) (length bindings-y))
466 (enter-binding-pairs (bindings-of-bound-term (car listx))
467 (bindings-of-bound-term (car listy)))
468 (alpha-equal-terms (term-of-bound-term (car listx))
469 (term-of-bound-term (car listy)))
470 (exit-binding-pairs (bindings-of-bound-term (car listx))
471 (bindings-of-bound-term (car listy)))))))
472 (alpha-equal-bound-term-lists (cdr listx) (cdr listy)))))
474 (alpha-equal-terms (termx termy)
475 (if (and (variable-p termx)
477 (equal-bindings (id-of-variable-term termx)
478 (id-of-variable-term termy))
479 (and (equal-operators-p (operator-of-term termx) (operator-of-term termy))
480 (alpha-equal-bound-term-lists (bound-terms-of-term termx)
481 (bound-terms-of-term termy))))))
485 (with-variable-invocation (alpha-equal-terms termx termy))))))
486 causes an assertion failure
487 The assertion (EQ (C::LAMBDA-TAIL-SET C::CALLER)
488 (C::LAMBDA-TAIL-SET (C::LAMBDA-HOME C::CALLEE))) failed.
490 Bob Rogers reports (1999-07-28 on cmucl-imp@cons.org) a smaller test
491 case with the same problem:
492 (defun parse-fssp-alignment ()
493 ;; Given an FSSP alignment file named by the argument . . .
494 (labels ((get-fssp-char ()
498 ;; Stub body, enough to tickle the bug.
499 (list (read-fssp-char)
503 ANSI specifies that the RESULT-TYPE argument of CONCATENATE must be
504 a subtype of SEQUENCE, but CONCATENATE doesn't check this properly:
505 (CONCATENATE 'SIMPLE-ARRAY #(1 2) '(3)) => #(1 2 3)
506 This also leads to funny behavior when derived type specifiers
507 are used, as originally reported by Milan Zamazal for CMU CL (on the
508 Debian bugs mailing list (?) 2000-02-27), then reported by Martin
509 Atzmueller for SBCL (2000-10-01 on sbcl-devel@lists.sourceforge.net):
510 (DEFTYPE FOO () 'SIMPLE-ARRAY)
511 (CONCATENATE 'FOO #(1 2) '(3))
512 => #<ARRAY-TYPE SIMPLE-ARRAY> is a bad type specifier for
514 The derived type specifier FOO should act the same way as the
515 built-in type SIMPLE-ARRAY here, but it doesn't. That problem
516 doesn't seem to exist for sequence types:
517 (DEFTYPE BAR () 'SIMPLE-VECTOR)
518 (CONCATENATE 'BAR #(1 2) '(3)) => #(1 2 3)
521 As reported by Winton Davies on a CMU CL mailing list 2000-01-10,
522 and reported for SBCL by Martin Atzmueller 2000-10-20: (TRACE GETHASH)
523 crashes SBCL. In general tracing anything which is used in the
524 implementation of TRACE is likely to have the same problem.
527 As reported by Daniel Solaz on cmucl-help@cons.org 2000-11-23,
528 SXHASH returns the same value for all non-STRUCTURE-OBJECT instances,
529 notably including all PCL instances. There's a limit to how much
530 SXHASH can do to return unique values for instances, but at least
531 it should probably look at the class name, the way that it does
532 for STRUCTURE-OBJECTs.
535 As reported by Martin Atzmueller on the sbcl-devel list 2000-11-22,
536 > There remains one issue, that is a bug in SBCL:
537 > According to my interpretation of the spec, the ":" and "@" modifiers
538 > should appear _after_ the comma-seperated arguments.
539 > Well, SBCL (and CMUCL for that matter) accept
540 > (ASSERT (STRING= (FORMAT NIL "~:8D" 1) " 1"))
541 > where the correct way (IMHO) should be
542 > (ASSERT (STRING= (FORMAT NIL "~8:D" 1) " 1"))
543 Probably SBCL should stop accepting the "~:8D"-style format arguments,
544 or at least issue a warning.
547 (probably related to bug #65; maybe related to bug #109)
548 The compiler doesn't like &OPTIONAL arguments in LABELS and FLET
550 (DEFUN FIND-BEFORE (ITEM SEQUENCE &KEY (TEST #'EQL))
551 (LABELS ((FIND-ITEM (OBJ SEQ TEST &OPTIONAL (VAL NIL))
552 (LET ((ITEM (FIRST SEQ)))
555 ((FUNCALL TEST OBJ ITEM)
558 (FIND-ITEM OBJ (REST SEQ) TEST (NCONC VAL `(,ITEM))))))))
559 (FIND-ITEM ITEM SEQUENCE TEST)))
560 from David Young's bug report on cmucl-help@cons.org 30 Nov 2000
561 causes sbcl-0.6.9 to fail with
562 error in function SB-KERNEL:ASSERT-ERROR:
563 The assertion (EQ (SB-C::LAMBDA-TAIL-SET SB-C::CALLER)
564 (SB-C::LAMBDA-TAIL-SET
565 (SB-C::LAMBDA-HOME SB-C::CALLEE))) failed.
568 (DECLAIM (OPTIMIZE ..)) doesn't work. E.g. even after
569 (DECLAIM (OPTIMIZE (SPEED 3))), things are still optimized with
570 the previous SPEED policy. This bug will probably get fixed in
571 0.6.9.x in a general cleanup of optimization policy.
574 (DECLAIM (OPTIMIZE ..)) doesn't work properly inside LOCALLY forms.
577 As reported by Martin Atzmueller on sbcl-devel 26 Dec 2000,
578 ANSI says that WITH-OUTPUT-TO-STRING should have a keyword
579 :ELEMENT-TYPE, but in sbcl-0.6.9 this is not defined for
580 WITH-OUTPUT-TO-STRING.
583 ANSI says in one place that type declarations can be abbreviated even
584 when the type name is not a symbol, e.g.
585 (DECLAIM ((VECTOR T) *FOOVECTOR*))
586 SBCL doesn't support this. But ANSI says in another place that this
587 isn't allowed. So it's not clear this is a bug after all. (See the
588 e-mail on cmucl-help@cons.org on 2001-01-16 and 2001-01-17 from WHN
592 as pointed out by Dan Barlow on sbcl-devel 2000-07-02:
593 The PICK-TEMPORARY-FILE-NAME utility used by LOAD-FOREIGN uses
594 an easily guessable temporary filename in a way which might open
595 applications using LOAD-FOREIGN to hijacking by malicious users
596 on the same machine. Incantations for doing this safely are
597 floating around the net in various "how to write secure programs
598 despite Unix" documents, and it would be good to (1) fix this in
599 LOAD-FOREIGN, and (2) hunt for any other code which uses temporary
600 files and make it share the same new safe logic.
603 Functions are assigned names based on the context in which they're
604 defined. This is less than ideal for the functions which are
605 used to implement CLOS methods. E.g. the output of
606 (DESCRIBE 'PRINT-OBJECT) lists functions like
607 #<FUNCTION "DEF!STRUCT (TRACE-INFO (:MAKE-LOAD-FORM-FUN SB-KERNEL:JUST-DUMP-IT-NORMALLY) (:PRINT-OBJECT #))" {1020E49}>
609 #<FUNCTION "MACROLET ((FORCE-DELAYED-DEF!METHODS NIL #))" {1242871}>
610 It would be better if these functions' names always identified
611 them as methods, and identified their generic functions and
615 RANDOM-INTEGER-EXTRA-BITS=10 may not be large enough for the RANDOM
616 RNG to be high quality near RANDOM-FIXNUM-MAX; it looks as though
617 the mean of the distribution can be systematically O(0.1%) wrong.
618 Just increasing R-I-E-B is probably not a good solution, since
619 it would decrease efficiency more than is probably necessary. Perhaps
620 using some sort of accept/reject method would be better.
623 (SUBTYPEP '(SATISFIES SOME-UNDEFINED-FUN) NIL)=>NIL,T (should be NIL,NIL)
626 Internally the compiler sometimes evaluates
627 (sb-kernel:type/= (specifier-type '*) (specifier-type t))
628 (I stumbled across this when I added an
629 (assert (not (eq type1 *wild-type*)))
630 in the NAMED :SIMPLE-= type method.) '* isn't really a type, and
631 in a type context should probably be translated to T, and so it's
632 probably wrong to ask whether it's equal to the T type and then (using
633 the EQ type comparison in the NAMED :SIMPLE-= type method) return NIL.
634 (I haven't tried to investigate this bug enough to guess whether
635 there might be any user-level symptoms.)
638 a latent cross-compilation/bootstrapping bug: The cross-compilation
639 host's CL:CHAR-CODE-LIMIT is used in target code in readtable.lisp
640 and possibly elsewhere. Instead, we should use the target system's
641 CHAR-CODE-LIMIT. This will probably cause problems if we try to
642 bootstrap on a system which uses a different value of CHAR-CODE-LIMIT
646 (subtypep '(or (integer -1 1)
650 (integer -1 1))) => NIL,T
651 An analogous problem with SINGLE-FLOAT and REAL types was fixed in
652 sbcl-0.6.11.22, but some peculiarites of the RATIO type make it
653 awkward to generalize the fix to INTEGER and RATIONAL. It's not
654 clear what's the best fix. (See the "bug in type handling" discussion
655 on cmucl-imp ca. 2001-03-22 and ca. 2001-02-12.)
658 Inconsistencies between derived and declared VALUES return types for
659 DEFUN aren't checked very well. E.g. the logic which successfully
660 catches problems like
661 (declaim (ftype (function (fixnum) float) foo))
663 (declare (type integer x))
664 (values x)) ; wrong return type, detected, gives warning, good!
666 (declaim (ftype (function (t) (values t t)) bar))
668 (values x)) ; wrong number of return values, no warning, bad!
669 The cause of this is seems to be that (1) the internal function
670 VALUES-TYPES-EQUAL-OR-INTERSECT used to make the check handles its
671 arguments symmetrically, and (2) when the type checking code was
672 written back when when SBCL's code was still CMU CL, the intent
674 (declaim (ftype (function (t) t) bar))
676 (values x x)) ; wrong number of return values; should give warning?
677 not be warned for, because a two-valued return value is considered
678 to be compatible with callers who expects a single value to be
679 returned. That intent is probably not appropriate for modern ANSI
680 Common Lisp, but fixing this might be complicated because of other
681 divergences between auld-style and new-style handling of
682 multiple-VALUES types. (Some issues related to this were discussed
683 on cmucl-imp at some length sometime in 2000.)
686 The facility for dumping a running Lisp image to disk gets confused
687 when run without the PURIFY option, and creates an unnecessarily large
688 core file (apparently representing memory usage up to the previous
689 high-water mark). Moreover, when the file is loaded, it confuses the
690 GC, so that thereafter memory usage can never be reduced below that
694 The TRACE facility can't be used on some kinds of functions.
695 (Basically, the breakpoint facility was incompletely implemented
696 in the X86 port of CMU CL, and hasn't been fixed in SBCL.)
699 In sbcl-0.6.11.41 (and in all earlier SBCL, and in CMU
700 CL), out-of-line structure slot setters are horribly inefficient
701 whenever the type of the slot is declared, because out-of-line
702 structure slot setters are implemented as closures to save space,
703 so the compiler doesn't compile the type test into code, but
704 instead just saves the type in a lexical closure and interprets it
706 A proper solution involves deciding whether it's really worth
707 saving space by implementing structure slot accessors as closures.
708 (If it's not worth it, the problem vanishes automatically. If it
709 is worth it, there are hacks we could use to force type tests to
710 be compiled anyway, and even shared. E.g. we could implement
711 an EQUAL hash table mapping from types to compiled type tests,
712 and save the appropriate compiled type test as part of each lexical
713 closure; or we could make the lexical closures be placeholders
714 which overwrite their old definition as a lexical closure with
715 a new compiled definition the first time that they're called.)
716 As a workaround for the problem, #'(SETF FOO) expressions can
717 be replaced with (EFFICIENT-SETF-FUNCTION FOO), where
718 (defmacro efficient-setf-function (place-function-name)
719 (or #+sbcl (and (sb-impl::info :function :accessor-for place-function-name)
720 ;; a workaround for the problem, encouraging the
721 ;; inline expansion of the structure accessor, so
722 ;; that the compiler can optimize its type test
723 (let ((new-value (gensym "NEW-VALUE-"))
724 (structure-value (gensym "STRUCTURE-VALUE-")))
725 `(lambda (,new-value ,structure-value)
726 (setf (,place-function-name ,structure-value)
728 ;; no problem, can just use the ordinary expansion
729 `(function (setf ,place-function-name))))
732 There's apparently a bug in CEILING optimization which caused
733 Douglas Crosher to patch the CMU CL version. Martin Atzmueller
734 applied the patches to SBCL and they didn't seem to cause problems
735 (as reported sbcl-devel 2001-05-04). However, since the patches
736 modify nontrivial code which was apparently written incorrectly
737 the first time around, until regression tests are written I'm not
738 comfortable merging the patches in the CVS version of SBCL.
741 As reported by Arthur Lemmens sbcl-devel 2001-05-05, ANSI
742 requires that SYMBOL-MACROLET refuse to rebind special variables,
743 but SBCL doesn't do this. (Also as reported by AL in the same
744 message, SBCL depended on this nonconforming behavior to build
745 itself, because of the way that **CURRENT-SEGMENT** was implemented.
746 As of sbcl-0.6.12.x, this dependence on the nonconforming behavior
747 has been fixed, but the nonconforming behavior remains.)
750 (DESCRIBE 'SB-ALIEN:DEF-ALIEN-TYPE) reports the macro argument list
754 in #<PACKAGE "SB-ALIEN">.
755 Macro-function: #<FUNCTION "DEF!MACRO DEF-ALIEN-TYPE" {19F4A39}>
756 Macro arguments: (#:whole-470 #:environment-471)
757 On Sat, May 26, 2001 09:45:57 AM CDT it was compiled from:
758 /usr/stuff/sbcl/src/code/host-alieneval.lisp
759 Created: Monday, March 12, 2001 07:47:43 AM CST
762 (TIME (ROOM T)) reports more than 200 Mbytes consed even for
763 a clean, just-started SBCL system. And it seems to be right:
764 (ROOM T) can bring a small computer to its knees for a *long*
765 time trying to GC afterwards. Surely there's some more economical
766 way to implement (ROOM T).
769 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
771 ;;; This file fails to compile.
772 ;;; Maybe this bug is related to bugs #65, #70 in the BUGS file.
773 (in-package :cl-user)
779 ;; Uncomment and it works
782 In SBCL 0.6.12.42, the problem is
783 internal error, failed AVER:
784 "(COMMON-LISP:EQ (SB!C::LAMBDA-TAIL-SET SB!C::CALLER)
785 (SB!C::LAMBDA-TAIL-SET (SB!C::LAMBDA-HOME SB!C::CALLEE)))"
788 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
790 ;;; The compiler is flushing the argument type test, and the default
791 ;;; case in the cond, so that calling with say a fixnum 0 causes a
793 (declaim (optimize (safety 2) (speed 3)))
795 (declare (type (or string stream) x))
796 (cond ((typep x 'string) 'string)
797 ((typep x 'stream) 'stream)
800 The symptom in sbcl-0.6.12.42 on OpenBSD is actually (TST 0)=>STREAM
801 (not the SIGBUS reported in the comment) but that's broken too;
802 type declarations are supposed to be treated as assertions unless
803 SAFETY 0, so we should be getting a TYPE-ERROR.
806 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
808 (in-package :cl-user)
809 ;;; Produces an assertion failures when compiled.
811 (declare (type (or (function (t) t) null) z))
812 (let ((z (or z #'identity)))
813 (declare (type (function (t) t) z))
815 The error in sbcl-0.6.12.42 is
816 internal error, failed AVER:
817 "(COMMON-LISP:NOT (COMMON-LISP:EQ SB!C::CHECK COMMON-LISP:T))"
820 reported by Martin Atzmueller 2001-06-25; taken from CMU CL bugs
821 collection; apparently originally reported by Bruno Haible
822 (in-package :cl-user)
823 ;;; From: Bruno Haible
824 ;;; Subject: scope of SPECIAL declarations
825 ;;; It seems CMUCL has a bug relating to the scope of SPECIAL
826 ;;; declarations. I observe this with "CMU Common Lisp 18a x86-linux
829 (declare (special x))
832 (declare (special x)) y)))
833 ;;; Gives: 0 (this should return 1 according to CLHS)
835 (declare (special x))
838 (declare (special x)) y)))
839 ;;; Gives: 1 (correct).
840 The reported results match what we get from the interpreter
844 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
846 (in-package :cl-user)
847 ;;; From: David Gadbois <gadbois@cyc.com>
849 ;;; Logical pathnames aren't externalizable.
851 (let ((tempfile "/tmp/test.lisp"))
852 (setf (logical-pathname-translations "XXX")
853 '(("XXX:**;*.*" "/tmp/**/*.*")))
854 (with-open-file (out tempfile :direction :output)
855 (write-string "(defvar *path* #P\"XXX:XXX;FOO.LISP\")" out))
856 (compile-file tempfile))
857 The error message in sbcl-0.6.12.42 is
859 ; (while making load form for #<SB-IMPL::LOGICAL-HOST "XXX">)
860 ; A logical host can't be dumped as a constant: #<SB-IMPL::LOGICAL-HOST "XXX">
863 reported by Martin Atzmueller 2001-06-25; originally from CMU CL bugs
865 (in-package :cl-user)
866 ;;; The following invokes a compiler error.
867 (declaim (optimize (speed 2) (debug 3)))
870 (unwind-protect nil)))
874 The error message in sbcl-0.6.12.42 is
875 internal error, failed AVER:
876 "(COMMON-LISP:EQ (SB!C::TN-ENVIRONMENT SB!C:TN) SB!C::TN-ENV)"
879 When the compiler inline expands functions, it may be that different
880 kinds of return values are generated from different code branches.
881 E.g. an inline expansion of POSITION generates integer results
882 from one branch, and NIL results from another. When that inline
883 expansion is used in a context where only one of those results
886 (aref *a1* (position x *a2*)))
887 and the compiler can't prove that the unacceptable branch is
888 never taken, then bogus type mismatch warnings can be generated.
889 If you need to suppress the type mismatch warnings, you can
890 suppress the inline expansion,
892 #+sbcl (declare (notinline position)) ; to suppress bug 117 bogowarnings
893 (aref *a1* (position x *a2*)))
894 or, sometimes, suppress them by declaring the result to be of an
897 (aref *a1* (the integer (position x *a2*))))
899 This is not a new compiler problem in 0.7.0, but the new compiler
900 transforms for FIND, POSITION, FIND-IF, and POSITION-IF make it
901 more conspicuous. If you don't need performance from these functions,
902 and the bogus warnings are a nuisance for you, you can return to
903 your pre-0.7.0 state of grace with
904 #+sbcl (declaim (notinline find position find-if position-if)) ; bug 117..
907 as reported by Eric Marsden on cmucl-imp@cons.org 2001-08-14:
908 (= (FLOAT 1 DOUBLE-FLOAT-EPSILON)
909 (+ (FLOAT 1 DOUBLE-FLOAT-EPSILON) DOUBLE-FLOAT-EPSILON)) => T
910 when of course it should be NIL. (He says it only fails for X86,
911 not SPARC; dunno about Alpha.)
913 Also, "the same problem exists for LONG-FLOAT-EPSILON,
914 DOUBLE-FLOAT-NEGATIVE-EPSILON, LONG-FLOAT-NEGATIVE-EPSILON (though
915 for the -negative- the + is replaced by a - in the test)."
917 Raymond Toy comments that this is tricky on the X86 since its FPU
918 uses 80-bit precision internally.
921 The compiler incorrectly figures the return type of
922 (DEFUN FOO (FRAME UP-FRAME)
929 This problem exists in CMU CL 18c too. When I reported it on
930 cmucl-imp@cons.org, Raymond Toy replied 23 Aug 2001 with
931 a partial explanation, but no fix has been found yet.
934 Even in sbcl-0.pre7.x, which is supposed to be free of the old
935 non-ANSI behavior of treating the function return type inferred
936 from the current function definition as a declaration of the
937 return type from any function of that name, the return type of NIL
938 is attached to FOO in 120a above, and used to optimize code which
942 There was some sort of screwup in handling of
943 (IF (NOT (IGNORE-ERRORS ..))). E.g.
945 (if (not (ignore-errors
946 (make-pathname :host "foo" :directory "!bla" :name "bar")))
948 (error "notunlessnot")))
949 The (NOT (IGNORE-ERRORS ..)) form evaluates to T, so this should be
950 printing "ok", but instead it's going to the ERROR. This problem
951 seems to've been introduced by MNA's HANDLER-CASE patch (sbcl-devel
952 2001-07-17) and as a workaround (put in sbcl-0.pre7.14.flaky4.12)
953 I reverted back to the old weird HANDLER-CASE code. However, I
954 think the problem looks like a compiler bug in handling RETURN-FROM,
955 so I left the MNA-patched code in HANDLER-CASE (suppressed with
956 #+NIL) and I'd like to go back to see whether this really is
957 a compiler bug before I delete this BUGS entry.
960 The *USE-IMPLEMENTATION-TYPES* hack causes bugs, particularly
961 (IN-PACKAGE :SB-KERNEL)
962 (TYPE= (SPECIFIER-TYPE '(VECTOR T))
963 (SPECIFIER-TYPE '(VECTOR UNDEFTYPE)))
964 Then because of this, the compiler bogusly optimizes
965 (TYPEP #(11) '(SIMPLE-ARRAY UNDEF-TYPE 1))
966 to T. Unfortunately, just setting *USE-IMPLEMENTATION-TYPES* to
967 NIL around sbcl-0.pre7.14.flaky4.12 didn't work: the compiler complained
968 about type mismatches (probably harmlessly, another instance of bug 117);
969 and then cold init died with a segmentation fault.
972 As of version 0.pre7.14, SBCL's implementation of MACROLET makes
973 the entire lexical environment at the point of MACROLET available
974 in the bodies of the macroexpander functions. In particular, it
975 allows the function bodies (which run at compile time) to try to
976 access lexical variables (which are only defined at runtime).
977 It doesn't even issue a warning, which is bad.
979 The SBCL behavior arguably conforms to the ANSI spec (since the
980 spec says that the behavior is undefined, ergo anything conforms).
981 However, it would be better to issue a compile-time error.
982 Unfortunately I (WHN) don't see any simple way to detect this
983 condition in order to issue such an error, so for the meantime
984 SBCL just does this weird broken "conforming" thing.
986 The ANSI standard says, in the definition of the special operator
988 The macro-expansion functions defined by MACROLET are defined
989 in the lexical environment in which the MACROLET form appears.
990 Declarations and MACROLET and SYMBOL-MACROLET definitions affect
991 the local macro definitions in a MACROLET, but the consequences
992 are undefined if the local macro definitions reference any
993 local variable or function bindings that are visible in that
995 Then it seems to contradict itself by giving the example
997 (macrolet ((fudge (z)
998 ;The parameters x and flag are not accessible
999 ; at this point; a reference to flag would be to
1000 ; the global variable of that name.
1001 ` (if flag (* ,z ,z) ,z)))
1002 ;The parameters x and flag are accessible here.
1006 The comment "a reference to flag would be to the global variable
1007 of the same name" sounds like good behavior for the system to have.
1008 but actual specification quoted above says that the actual behavior
1012 (as reported by Gabe Garza on cmucl-help 2001-09-21)
1014 (defun test-pred (x y)
1018 (func (lambda () x)))
1019 (print (eq func func))
1020 (print (test-pred func func))
1021 (delete func (list func))))
1022 Now calling (TEST-CASE) gives output
1025 (#<FUNCTION {500A9EF9}>)
1026 Evidently Python thinks of the lambda as a code transformation so
1027 much that it forgets that it's also an object.
1030 (fixed in 0.pre7.41)
1033 The DEFSTRUCT section of the ANSI spec, in the :CONC-NAME section,
1034 specifies a precedence rule for name collisions between slot accessors of
1035 structure classes related by inheritance. As of 0.7.0, SBCL still
1039 insufficient syntax checking in MACROLET:
1041 (macrolet ((defmacro bar (z) `(+ z z)))
1043 shouldn't compile without error (because of the extra DEFMACRO symbol).
1046 As of sbcl-0.pre7.86.flaky7.3, the cross-compiler, and probably
1047 the CL:COMPILE function (which is based on the same %COMPILE
1048 mechanism) get confused by
1050 (labels ((sxhash-number (x)
1052 (fixnum (sxhash x)) ; through DEFTRANSFORM
1053 (integer (sb!bignum:sxhash-bignum x))
1054 (single-float (sxhash x)) ; through DEFTRANSFORM
1055 (double-float (sxhash x)) ; through DEFTRANSFORM
1056 #!+long-float (long-float (error "stub: no LONG-FLOAT"))
1057 (ratio (let ((result 127810327))
1058 (declare (type fixnum result))
1059 (mixf result (sxhash-number (numerator x)))
1060 (mixf result (sxhash-number (denominator x)))
1062 (complex (let ((result 535698211))
1063 (declare (type fixnum result))
1064 (mixf result (sxhash-number (realpart x)))
1065 (mixf result (sxhash-number (imagpart x)))
1067 (sxhash-recurse (x &optional (depthoid +max-hash-depthoid+))
1068 (declare (type index depthoid))
1071 (if (plusp depthoid)
1072 (mix (sxhash-recurse (car x) (1- depthoid))
1073 (sxhash-recurse (cdr x) (1- depthoid)))
1076 (if (typep x 'structure-object)
1078 (sxhash ; through DEFTRANSFORM
1079 (class-name (layout-class (%instance-layout x)))))
1081 (symbol (sxhash x)) ; through DEFTRANSFORM
1082 (number (sxhash-number x))
1085 (simple-string (sxhash x)) ; through DEFTRANSFORM
1086 (string (%sxhash-substring x))
1087 (bit-vector (let ((result 410823708))
1088 (declare (type fixnum result))
1089 (dotimes (i (min depthoid (length x)))
1090 (mixf result (aref x i)))
1092 (t (logxor 191020317 (sxhash (array-rank x))))))
1095 (sxhash (char-code x)))) ; through DEFTRANSFORM
1097 (sxhash-recurse x)))
1098 complaining "function called with two arguments, but wants exactly
1099 one" about SXHASH-RECURSE. (This might not be strictly a new bug,
1100 since IIRC post-fork CMU CL has also had problems with &OPTIONAL
1101 arguments in FLET/LABELS: it might be an old Python bug which is
1102 only exercised by the new arrangement of the SBCL compiler.)
1106 (DEFUN FOO () (CATCH 0 (PRINT 1331)))
1108 #<SB-C:TN '0!1> is not valid as the second argument to VOP:
1109 SB-C:MAKE-CATCH-BLOCK,
1110 since the TN's primitive type SB-VM::POSITIVE-FIXNUM doesn't allow
1111 any of the SCs allowed by the operand restriction:
1112 (SB-VM::DESCRIPTOR-REG)
1113 The (CATCH 0 ...) construct is bad style (because of unportability
1114 of EQ testing of numbers) but it is legal, and shouldn't cause an
1115 internal compiler error. (This error occurs in sbcl-0.6.13 and in
1116 0.pre7.86.flaky7.14.)
1119 Ideally, uninterning a symbol would allow it, and its associated
1120 FDEFINITION and PROCLAIM data, to be reclaimed by the GC. However,
1121 at least as of sbcl-0.7.0, this isn't the case. Information about
1122 FDEFINITIONs and PROCLAIMed properties is stored in globaldb.lisp
1123 essentially in ordinary (non-weak) hash tables keyed by symbols.
1124 Thus, once a system has an entry in this system, it tends to live
1125 forever, even when it is uninterned and all other references to it
1129 (reported by Arnaud Rouanet on cmucl-imp 2001-12-18)
1130 (defmethod foo ((x integer))
1132 (defmethod foo :around ((x integer))
1134 (call-next-method)))
1135 Now (FOO 3) should return 3, but instead it returns 4.
1138 (SB-DEBUG:BACKTRACE) output should start with something
1139 including the name BACKTRACE, not (as in 0.pre7.88)
1140 just "0: (\"hairy arg processor\" ...)". Until about
1141 sbcl-0.pre7.109, the names in BACKTRACE were all screwed
1142 up compared to the nice useful names in sbcl-0.6.13.
1143 Around sbcl-0.pre7.109, they were mostly fixed by using
1144 NAMED-LAMBDA to implement DEFUN. However, there are still
1145 some screwups left, e.g. as of sbcl-0.pre7.109, there are
1146 still some functions named "hairy arg processor" and
1147 "SB-INT:&MORE processor".
1150 (reported by Alexey Dejneka sbcl-devel 2002-01-03)
1152 SUBTYPEP does not work well with redefined classes:
1154 * (defclass a () ())
1156 * (defclass b () ())
1161 * (defclass b (a) ())
1166 * (defclass b () ())
1175 Pretty-printing nested backquotes doesn't work right, as
1176 reported by Alexey Dejneka sbcl-devel 2002-01-13:
1178 ``(FOO SB-IMPL::BACKQ-COMMA-AT S)
1179 * (lisp-implementation-version)
1183 (as reported by Lynn Quam on cmucl-imp ca. 2002-01-16)
1184 %NATURALIZE-C-STRING conses a lot, like 16 bytes per byte
1185 of the naturalized string. We could probably port the patches
1186 from the cmucl-imp mailing list.
1189 (reported by Jesse Bouwman 2001-10-24 through the unfortunately
1190 prominent SourceForge web/db bug tracking system, which is
1191 unfortunately not a reliable way to get a timely response from
1192 the SBCL maintainers)
1193 In the course of trying to build a test case for an
1194 application error, I encountered this behavior:
1195 If you start up sbcl, and then lay on CTRL-C for a
1196 minute or two, the lisp process will eventually say:
1197 %PRIMITIVE HALT called; the party is over.
1198 and throw you into the monitor. If I start up lisp,
1199 attach to the process with strace, and then do the same
1200 (abusive) thing, I get instead:
1201 access failure in heap page not marked as write-protected
1202 and the monitor again. I don't know enough to have the
1203 faintest idea of what is going on here.
1204 This is with sbcl 6.12, uname -a reports:
1205 Linux prep 2.2.19 #4 SMP Tue Apr 24 13:59:52 CDT 2001 i686 unknown
1206 I (WHN) have verified that the same thing occurs on sbcl-0.pre7.141
1207 under OpenBSD 2.9 on my X86 laptop. Do be patient when you try it:
1208 it took more than two minutes (but less than five) for me.
1211 (This was once known as IR1-4, but it lived on even after the
1212 IR1 interpreter went to the big bit bucket in the sky.)
1213 The system accepts DECLAIM in most places where DECLARE would be
1214 accepted, without even issuing a warning. ANSI allows this, but since
1215 it's fairly easy to mistype DECLAIM instead of DECLARE, and the
1216 meaning is rather different, and it's unlikely that the user
1217 has a good reason for doing DECLAIM not at top level, it would be
1218 good to issue a STYLE-WARNING when this happens. A possible
1219 fix would be to issue STYLE-WARNINGs for DECLAIMs not at top level,
1220 or perhaps to issue STYLE-WARNINGs for any EVAL-WHEN not at top level.
1221 [This is considered an IR1-interpreter-related bug because until
1222 EVAL-WHEN is rewritten, which won't happen until after the IR1
1223 interpreter is gone, the system's notion of what's a top-level form
1224 and what's not will remain too confused to fix this problem.]
1227 ANSI allows types `(COMPLEX ,FOO) to use very hairy values for
1228 FOO, e.g. (COMPLEX (AND REAL (SATISFIES ODDP))). The old CMU CL
1229 COMPLEX implementation didn't deal with this, and hasn't been
1230 upgraded to do so. (This doesn't seem to be a high priority
1231 conformance problem, since seems hard to construct useful code
1234 DEFUNCT CATEGORIES OF BUGS
1236 These numbers were used for bugs related to the old IR1
1237 interpreter. The # values reached 6 before the category