;;;; -*- coding: utf-8; -*-
+changes in sbcl-1.0.14 relative to sbcl-1.0.13:
+ * bug fix: RESOLVE-CONFLICT (and the other name conflict machinery)
+ is now actually exported from SB-EXT as documented. (reported by
+ Maciej Katafiasz)
+
+changes in sbcl-1.0.13 relative to sbcl-1.0.12:
+ * minor incompatible change: RUN-PROGRAM now uses execvp(3) to find
+ an executable in the search path, and does so in the child
+ process's PATH. The function FIND-EXECUTABLE-IN-SEARCH-PATH has
+ been removed; it can be found in the CVS history, for somebody who
+ needs that search behavior (see the manual).
+ * minor incompatible change: compiler policy re. weakening type
+ checks has changed: now type checks are weakened on if SAFETY < 2
+ and SAFETY < SPEED.
+ * SB-EXT:NATIVE-NAMESTRING takes a new keyword AS-FILE, forcing
+ unparsing of directory pathnames as files. Analogously,
+ SB-EXT:PARSE-NATIVE-NAMESTRING takes an AS-DIRECTORY, forcing a
+ filename to parse into a directory pathname.
+ * enhancement: implicit generic function creation now signals a
+ specific style-warning IMPLICIT-GENERIC-FUNCTION-WARNING, which
+ users can bind handlers for and muffle around calls to LOAD.
+ * enhancement: RUN-PROGRAM allows unicode arguments and environments
+ to be used (using the default stream external format), and allows
+ non-simple strings to be used. (thanks to Harald Hanche-Olsen)
+ * optimization: COPY-SEQ, FILL, and SUBSEQ are 30-80% faster for
+ strings and vectors whose element-type or simplicity is not fully
+ known at compile-time.
+ * optimization: STRING-TRIM and related functions no longer allocate
+ a new string when no trimming needs to be performed. These functions
+ are also faster than before when the input string has been declared
+ as a simple-string.
+ * optimization: READ-SEQUENCE on simple-strings is up to 80% faster.
+ * optimization: READ-LINE is significantly faster for files containing
+ long lines.
+ * optimization: non-open coded uses of character comparison operators
+ (e.g. char=) no longer cons when called with more than one parameter
+ on platforms supporting dynamic-extent allocation.
+ * bug fix: READ-SEQUENCE on composite stream wrapping a Gray stream
+ with STREAM-ELEMENT-TYPE (UNSIGNED-BYTE 8) signalled an error.
+ * bug fix: COPY-SEQ on lists did not signal a type-error on improper
+ lists in safe code.
+ * bug fix: some sequence functions elided bounds checking when
+ SPEED > SAFETY.
+ * bug fix: too liberal weakening of union-type checks when SPEED >
+ SAFETY.
+ * bug fix: more bogus fixnum declarations in ROOM implementation
+ have been fixed.
+
+changes in sbcl-1.0.12 relative to sbcl-1.0.11:
+ * new feature: MAKE-HASH-TABLE now experimentally accepts a
+ :SYNCHRONIZED argument, which makes the hash-table safe for
+ concurrent accesses (but not iteration.) See also:
+ SB-EXT:WITH-LOCKED-HASH-TABLE, and
+ SB-EXT:HASH-TABLE-SYNCHRONIZED-P.
+ * optimization: CONCATENATE on strings is an order of magnitue faster
+ in code compiled with (> SPEED SPACE).
+ * optimization: SUBSEQ is ~50% faster on lists.
+ * bug fix: bug 417 fixed -- source location reporting is now more robust.
+ * bug fix: SUBSEQ on a list will now correctly signal an error if if
+ END is smaller then START.
+ * bug fix: SB-PROFILE will no longer report extra consing for nested
+ calls to profiled functions.
+ * bug fix: ROOM implementation had bogus fixnum declarations which
+ could cause type-errors when calling ROOM on large images.
+ * bug fix: if file compilation is aborted, the partial fasl is now
+ deleted, and COMPILE-FILE returns NIL as the primary value.
+ * bug fix: number of thread safety issues relating to SBCL's internal
+ hash-table usage have been fixed.
+ * bug fix: SB-SYS:WITH-PINNED-OBJECTS could cause garbage values to
+ be returned from its body when the values were being returned
+ using unknown-values return convection and the W-P-O was wrapped
+ inside an UNWIND-PROTECT.
+ * bug fix: sb-posix should now compile again under Windows, enabling
+ slime to work again.
+
changes in sbcl-1.0.11 relative to sbcl-1.0.10:
* incompatible change: hash-table accessor functions are no longer
automatically protected by locks. Concurrent accesses on the same hash-table
locking at the correct granularity. In the current implementation it is
still safe to have multiple readers access the same table, but it's not
guaranteed that this property will be maintained in future releases.
+ * minor incompatible change: (SETF MUTEX-VALUE) is not longer supported,
+ and will signal an error at runtime.
+ * enhancement: SB-THREAD package now exports a semaphore interface.
* enhancement: CONS can now stack-allocate on x86 and
x86-64. (Earlier LIST and LIST* supported stack-allocation, but
CONS did not.)
* enhancement: dynamic-extent support has been extended to support
cases where there are multiple possible sources for the stack
allocated value.
+ * optimization: RELEASE-MUTEX no longer needs to perform a syscall
+ if the mutex is uncontested on Linux.
* bug fix: symbol-macro expansion now uses the *MACROEXPAND-HOOK*
as specified by the CLHS. (thanks to Tobias Rittweiler)
+ * bug fix: NaN comparison now works on x86-64.
+ * bug fix: CLOSE :ABORT T on a stream with pending output now
+ works.
+ * bug fix: instances of non-standard metaclasses using standard
+ instance structure protocol sometimes missed the slot type checks
+ in safe code.
+ * bug fix: known functions can be inlined in high-debug code.
changes in sbcl-1.0.10 relative to sbcl-1.0.9:
* minor incompatible change: the MSI installer on Windows no longer
projects / sbcl.git / blobdiff