From: William Harold Newman Date: Mon, 22 Jul 2002 20:22:41 +0000 (+0000) Subject: 0.7.5.22: X-Git-Url: http://repo.macrolet.net/gitweb/?a=commitdiff_plain;h=9728093863d1ed201719d1f7ef61b9df29bb1d44;p=sbcl.git 0.7.5.22: deleted email addresses in the wake of autospam to cmucl-imp ("Attn: If you find bugs in CMU CL please report them to") --- diff --git a/BUGS b/BUGS index 7f5faab..b53b355 100644 --- a/BUGS +++ b/BUGS @@ -1456,6 +1456,18 @@ WORKAROUND: (INTEGER 1296 1296) ...)>)[:EXTERNAL] +189: "ignored NOTINLINE for functions defined by FLET or LABELS" + According to the ANSI definition of the NOTINLINE declaration, + NOTINLINE specifies that it is undesirable to compile the functions + named by FUNCTION-NAMES in-line. A compiler is not free to ignore + this declaration; calls to the specified functions must be implemented + as out-of-line subroutine calls. + However, as of sbcl-0.7.5.22, Python ignores this declaration for + functions defined by LABELS and FLET, and merrily optimizes away the + LAMBDAs. (This is an annoyance not just for language lawyers, but for + people who want a useful BACKTRACE for functions which, for whatever + reason, are constrained to be implemented as LABELS or LET.) + DEFUNCT CATEGORIES OF BUGS IR1-#: These labels were used for bugs related to the old IR1 interpreter. diff --git a/CREDITS b/CREDITS index be40848..5937017 100644 --- a/CREDITS +++ b/CREDITS @@ -629,3 +629,4 @@ RAM Robert MacLachlan WHN William ("Bill") Newman CSR Christophe Rhodes PVE Peter Van Eynde +PW Paul Werkowski \ No newline at end of file diff --git a/doc/sbcl.1 b/doc/sbcl.1 index ffe4b37..e28d861 100644 --- a/doc/sbcl.1 +++ b/doc/sbcl.1 @@ -485,8 +485,12 @@ handled specially by certain type expanders.) .SH REPORTING BUGS -To report a bug, please send mail to sbcl-help@lists.sourceforge.net -or sbcl-devel@lists.sourceforge.net. +To report a bug, please send mail to the mailing lists sbcl-help or +sbcl-devel. You can find the complete mailing list addresses on the +web pages, . (You may also find fancy +SourceForge bug-tracking machinery there, but don't be fooled. As of +2002-07-25 anyway, we don't actively monitor that machinery and just +haven't been able to figure out how to turn it off.) As with any software bug report, it's most helpful if you can provide enough information to reproduce the symptoms reliably, and if you say diff --git a/src/code/cross-float.lisp b/src/code/cross-float.lisp index 7fcb3e0..e7236c1 100644 --- a/src/code/cross-float.lisp +++ b/src/code/cross-float.lisp @@ -185,10 +185,9 @@ ;;; when trying to optimize the EXPT forms in the MAKE-FOO-FLOAT ;;; functions below. See the message ;;; Subject: Re: Compiler bug? -;;; From: Raymond Toy +;;; From: Raymond Toy ;;; Date: 28 Mar 2001 08:19:59 -0500 -;;; Message-ID: <4nvgou3u9s.fsf@rtp.ericsson.se> -;;; on the cmucl-imp@cons.org mailing list. Once the CMU CL folks +;;; on the cmucl-imp mailing list. Once the CMU CL folks ;;; make a bug-fix release, we can get rid of this and go back to ;;; calling EXPT directly. -- WHN 2001-04-05 (defun kludge-opaque-expt (x y) diff --git a/src/code/irrat.lisp b/src/code/irrat.lisp index 98b118c..ac8b805 100644 --- a/src/code/irrat.lisp +++ b/src/code/irrat.lisp @@ -596,7 +596,7 @@ ;;;; ;;;; The original CMU CL code requested: ;;;; Please send any bug reports, comments, or improvements to -;;;; Raymond Toy at toy@rtp.ericsson.se. +;;;; Raymond Toy at . ;;; FIXME: In SBCL, the floating point infinity constants like ;;; SB!EXT:DOUBLE-FLOAT-POSITIVE-INFINITY aren't available as diff --git a/src/code/reader.lisp b/src/code/reader.lisp index 821a9e4..2ad7a3b 100644 --- a/src/code/reader.lisp +++ b/src/code/reader.lisp @@ -1207,7 +1207,7 @@ (#\D 'double-float) (#\L 'long-float))) num) - ;; toy@rtp.ericsson.se: We need to watch out if the + ;; Raymond Toy writes: We need to watch out if the ;; exponent is too small or too large. We add enough to ;; EXPONENT to make it within range and scale NUMBER ;; appropriately. This should avoid any unnecessary diff --git a/src/code/target-format.lisp b/src/code/target-format.lisp index 8d87aa4..bf26753 100644 --- a/src/code/target-format.lisp +++ b/src/code/target-format.lisp @@ -576,7 +576,7 @@ ;;; errors. As for now, we let the user get away with it, and merely guarantee ;;; that at least one significant digit will appear. -;;; toy@rtp.ericsson.se: The Hyperspec seems to say that the exponent +;;; Raymond Toy writes: The Hyperspec seems to say that the exponent ;;; marker is always printed. Make it so. Also, the original version ;;; causes errors when printing infinities or NaN's. The Hyperspec is ;;; silent here, so let's just print out infinities and NaN's instead @@ -651,7 +651,7 @@ w 1 0 #\space t))) (format-princ stream number nil nil w 1 0 pad))) -;;; toy@rtp.ericsson.se: Same change as for format-exp-aux. +;;; Raymond Toy writes: same change as for format-exp-aux (defun format-general-aux (stream number w d e k ovf pad marker atsign) (if (and (floatp number) (or (float-infinity-p number) diff --git a/src/code/target-pathname.lisp b/src/code/target-pathname.lisp index 760399a..5073954 100644 --- a/src/code/target-pathname.lisp +++ b/src/code/target-pathname.lisp @@ -479,11 +479,11 @@ a host-structure or string." (default-host (if defaults (%pathname-host defaults) (pathname-host *default-pathname-defaults*))) - ;; toy@rtp.ericsson.se: CLHS says make-pathname can take a + ;; Raymond Toy writes: CLHS says make-pathname can take a ;; string (as a logical-host) for the host part. We map that ;; string into the corresponding logical host structure. ;; - ;; pw@snoopy.mv.com: + ;; Paul Werkowski writes: ;; HyperSpec says for the arg to MAKE-PATHNAME; ;; "host---a valid physical pathname host. ..." ;; where it probably means -- a valid pathname host. diff --git a/src/compiler/ir2tran.lisp b/src/compiler/ir2tran.lisp index 01e908b..0243abc 100644 --- a/src/compiler/ir2tran.lisp +++ b/src/compiler/ir2tran.lisp @@ -979,7 +979,7 @@ ;;; list. (defvar *always-optimized-away* '(;; This should always be DEFTRANSFORMed away, but wasn't in a bug - ;; reported to cmucl-imp@cons.org 2000-06-20. + ;; reported to cmucl-imp 2000-06-20. %instance-ref ;; These should always turn into VOPs, but wasn't in a bug which ;; appeared when LTN-POLICY stuff was being tweaked in diff --git a/src/compiler/sparc/arith.lisp b/src/compiler/sparc/arith.lisp index de06b78..b9c1c70 100644 --- a/src/compiler/sparc/arith.lisp +++ b/src/compiler/sparc/arith.lisp @@ -172,8 +172,7 @@ ;;; Special case fixnum + and - that trap on overflow. Useful when we ;;; don't know that the output type is a fixnum. -;;; I (toy@rtp.ericsson.se) took these out. They don't seem to be -;;; used anywhere at all. +;;; I (Raymond Toy) took these out. They don't seem to be used anywhere at all. #+nil (progn (define-vop (+/fixnum fast-+/fixnum=>fixnum) diff --git a/src/compiler/sparc/float.lisp b/src/compiler/sparc/float.lisp index 5834443..329d8be 100644 --- a/src/compiler/sparc/float.lisp +++ b/src/compiler/sparc/float.lisp @@ -1273,7 +1273,7 @@ ;; The desired FP mode data is in the least significant 32 ;; bits, which is stored at the next higher word in memory. (loadw res nfp (+ offset 4)) - ;; Is this nop needed? (toy@rtp.ericsson.se) + ;; Is this nop needed? -- rtoy (inst nop)))) (define-vop (set-floating-point-modes) diff --git a/src/compiler/sparc/insts.lisp b/src/compiler/sparc/insts.lisp index a3fdce7..bd3589c 100644 --- a/src/compiler/sparc/insts.lisp +++ b/src/compiler/sparc/insts.lisp @@ -1675,8 +1675,8 @@ about function addresses and register values.") (define-unary-fp-inst fxtoq #b010001100 :reads :fsr :extended t) ; v9 - ;; I (toy@rtp.ericsson.se) don't think these f{sd}toir instructions - ;; exist on any Ultrasparc, but I only have a V9 manual. The code in + ;; I (Raymond Toy) don't think these f{sd}toir instructions exist on + ;; any Ultrasparc, but I only have a V9 manual. The code in ;; float.lisp seems to indicate that they only existed on non-sun4 ;; machines (sun3 68K machines?). (define-unary-fp-inst fstoir #b011000001 :reads :fsr) diff --git a/version.lisp-expr b/version.lisp-expr index 06f81e0..0caf24a 100644 --- a/version.lisp-expr +++ b/version.lisp-expr @@ -18,4 +18,4 @@ ;;; for internal versions, especially for internal versions off the ;;; main CVS branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".) -"0.7.5.21" +"0.7.5.22"