Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Update of /cvsroot/sbcl/sbcl
In directory sfp-cvsdas-3.v30.ch3.sourceforge.com:/tmp/cvs-serv32398
188.8.131.52: PPC character handling fixes.
* SAP-REF-32LE referred to SAP-REF-16 instead of SAP-REF-16LE on
non-x86oid platforms, incorrect for all big-endian targets.
* The immediate-character MOVE function was using a 16-bit-only
load instruction, which was insufficient for unicode operation.
* The -c (constant) character compare VOPs use a compare
instruction with a 16-bit immediate field. Disabled on unicode
(there's no good way to conditionally use them when the code
point of the constant character fits a signed-byte 16).
* Cleaned up some external-format.impure.lisp test-cases, adding
with-test and names as needed.
RCS file: /cvsroot/sbcl/sbcl/NEWS,v
retrieving revision 1.1757
retrieving revision 1.1758
diff -u -d -r1.1757 -r1.1758
--- NEWS 30 Apr 2010 16:53:16 -0000 1.1757
+++ NEWS 1 May 2010 00:15:10 -0000 1.1758
@@ -8,6 +8,9 @@
* bug fix: Scrub control stack after scavenging in gencgc on non-x86oid
platforms, preventing the GC from seeing stale pointers on the control
stack in subsequent GCs (which would, and does, break invariants).
+ * bug fix: 32-bit unicode external formats now work on big-endian systems.
+ * bug fix: Literal characters with code points greater than about 32767
+ now work on PPC UNICODE builds.
changes in sbcl-1.0.38 relative to sbcl-1.0.37:
* incompatible change: Thread names are now restricted to SIMPLE-STRINGs
RCS file: /cvsroot/sbcl/sbcl/version.lisp-expr,v
retrieving revision 1.4872
retrieving revision 1.4873
diff -u -d -r1.4872 -r1.4873
--- version.lisp-expr 30 Apr 2010 16:53:16 -0000 1.4872
+++ version.lisp-expr 1 May 2010 00:15:10 -0000 1.4873
@@ -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".)