1.0.13.22: text tweaks

	* logged a bug
	* searched for sbcl-devel references and added notes about
	  the need to subscribe (since the mailman bounce message is
	  particularly unhelpful, and I periodically get mail from
	  frustrated would-be posters)
	* fixed a few typoes
	* revised a few passages, and completely gave up on trying to
	  summarize SBCL performance in a paragraph in the man page

diff --git a/BUGS b/BUGS
index 4090ef5..c3a824d 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -1862,3 +1862,21 @@ WORKAROUND:
               ((lambda (f g) (eval `(progn ,f ,g (values 4 5 6)))) #'mget #'mset))))))
 
   (ASSERT (EQUAL (BUG419) '(1 2 3 4 5 6))) => failure
+
+420: The MISC.556 test from gcl/ansi-tests/misc.lsp fails hard.
+
+In sbcl-1.0.13 on Linux/x86, executing 
+       (FUNCALL
+        (COMPILE NIL
+                 '(LAMBDA (P1 P2)
+                    (DECLARE
+                     (OPTIMIZE (SPEED 1) (SAFETY 0) (DEBUG 0) (SPACE 0))
+                     (TYPE (MEMBER 8174.8604) P1) (TYPE (MEMBER -95195347) P2))
+                    (FLOOR P1 P2)))
+        8174.8604 -95195347)
+interactively causes
+  SB-SYS:MEMORY-FAULT-ERROR: Unhandled memory fault at #x8.
+The gcl/ansi-tests/doit.lisp program terminates prematurely shortly after
+MISC.556 by falling into gdb with
+  fatal error encountered in SBCL pid 2827: Unhandled SIGILL
+unless the MISC.556 test is commented out.

diff --git a/README b/README
index 4670fb1..336de6f 100644 (file)
--- a/README
+++ b/README
@@ -22,6 +22,8 @@ If you'd like to make suggestions, report a bug, or help to improve the
 system, please send mail to one of the mailing lists:
   sbcl-help@lists.sourceforge.net
   sbcl-devel@lists.sourceforge.net
+Note that as a spam reduction measure you must subscribe to the lists
+before you can post.
 
 
 SYSTEM-SPECIFIC HINTS

diff --git a/doc/README b/doc/README
index 36bc692..bf901a4 100644 (file)
--- a/doc/README
+++ b/doc/README
@@ -1,5 +1,5 @@
-SBCL is -- ahem! -- not completely documented at this point. What can
-I say? Help with documentation might not be refused.:-)
+SBCL is -- ahem! -- imperfectly documented. What can we say? Help with
+documentation might not be refused.:-)
 
 There is a Unix man page, sbcl.1.
 

diff --git a/doc/manual/intro.texinfo b/doc/manual/intro.texinfo
index ca6ab0f..2795d9a 100644 (file)
--- a/doc/manual/intro.texinfo
+++ b/doc/manual/intro.texinfo
@@ -30,8 +30,8 @@ distribution.
 
 The recommended way to report bugs is through the @cite{sbcl-help} or
 @cite{sbcl-devel} mailing lists. For mailing list addresses,
-see @ref{SBCL Homepage}.
-
+see @ref{SBCL Homepage}; note that as a spam-reduction measure you
+must subscribe before you can post.
 
 
 

diff --git a/doc/sbcl.1 b/doc/sbcl.1
index c368b58..621eaef 100644 (file)
--- a/doc/sbcl.1
+++ b/doc/sbcl.1
@@ -62,9 +62,9 @@ Many people like to run SBCL, like other Lisp systems, as a subprocess
 under Emacs. The Emacs "Slime" and "ilisp" modes provide many
 convenient features, like command line editing, tab completion, and
 various kinds of coupling between Common Lisp source files and the
-interactive SBCL subprocess, but they can be somewhat fragile wrt.
-packages and readtables, in which case SBCL in the Emacs "shell" mode
-can a useful substitute.
+interactive SBCL subprocess, but they can be somewhat fragile with
+respect to packages and readtables, in which case SBCL in the Emacs
+"shell" mode can be a useful substitute.
 
 .SH OVERVIEW
 
@@ -79,7 +79,7 @@ the BUGS section below.
 SBCL also includes various non-ANSI extensions, described more fully
 in the User Manual.  Some of these are in the base system and others
 are "contrib" modules loaded on request using \f(CRREQUIRE\fR.  For
-example, to load the \f(CRSB\-BSD\-SOCKETS\fR module that providces
+example, to load the \f(CRSB\-BSD\-SOCKETS\fR module that provides
 TCP/IP connectivity,
 \f(CR
    * (require \(aqasdf)
@@ -145,8 +145,9 @@ and functions (\fIe.g.\fR \f(CRLETF\fR, \f(CRITERATE\fR, \f(CRMEMQ\fR,
 \f(CRREQUIRED\-ARGUMENT\fR), and many others.
 
 SBCL inplements multithreading, but in a completely different fashion
-from CMU CL: see the User Manual for details.  As of 0.8.5 this is
-considered beta-quality and must be explicitly enabled at build time.
+from CMU CL: see the User Manual for details. As of 1.0.13 this is
+still considered beta-quality and must be explicitly enabled at build
+time.
 
 SBCL has retained some extensions from its parent CMU CL. Many of the
 retained extensions are in these categories:
@@ -208,15 +209,6 @@ but very useful principle that "declarations are assertions", \fIi.e.\fR
 type declarations should be checked at runtime unless the user
 explicitly tells the system that speed is more important than safety.
 
-The compiler reportedly produces pretty good code for modern CPU
-architectures which have lots of registers, but its code for the X86
-is marred by many extra loads and stores to stack-based temporary
-variables. Because of this, and because of the extra levels of
-indirection in Common Lisp relative to C, the performance of SBCL
-isn't going to impress people who are impressed by small constant
-factors. However, even on the X86 it tends to be faster than byte
-interpreted languages (and can be a lot faster).
-
 The compiled code uses garbage collection to automatically
 manage memory. The garbage collector implementation varies considerably
 from CPU to CPU. In particular, on some CPUs the GC is nearly exact,
@@ -431,11 +423,12 @@ point result as a function value) is a fundamentally slow operation.
 
 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 at <\f(CRhttp://sbcl.sourceforge.net/\fR>.  (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 it exists only because we haven't been able to figure
-out how to turn it off.)
+web pages at <\f(CRhttp://sbcl.sourceforge.net/\fR>; note that as a
+spam reduction measure you must subscribe to the lists before you can
+post. (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 it exists only because we 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/version.lisp-expr b/version.lisp-expr
index e8fcfbf..ab5a45b 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.13.21"
+"1.0.13.22"