From: Alastair Bridgewater Date: Fri, 3 Sep 2010 00:26:50 +0000 (+0000) Subject: 1.0.42.26: tests: Fix broken :fails-on clause for a dynamic-extent.impure test X-Git-Url: http://repo.macrolet.net/gitweb/?a=commitdiff_plain;h=7eefc129d5bc364db9238bc157c9c505231df2e3;p=sbcl.git 1.0.42.26: tests: Fix broken :fails-on clause for a dynamic-extent.impure test * Test case dynamic-extent.impure.lisp / (:NO-CONSING :HASH-TABLES) fails on threaded PPC targets, but because the clause was not quoted, it evaluated to all threaded targets, which was wrong. My mistake, too. * Added NEWS entry forgotten in 1.0.42.23, also my mistake. --- diff --git a/NEWS b/NEWS index 2c12e6b..ad3cac1 100644 --- a/NEWS +++ b/NEWS @@ -34,6 +34,9 @@ changes relative to sbcl-1.0.42 (lp#598986, thanks to Stas Boukarev) * bug fix: the compiler occasionally inlined references from incompatible environments occurs. (lp#308951) + * bug fix: the compiler threw an error when trying to compile a local + function (labels or flet) known to take a specialized complex argument. + (not in launchpad, reported by sykopomp in #lispgames) changes in sbcl-1.0.42 relative to sbcl-1.0.41 diff --git a/tests/dynamic-extent.impure.lisp b/tests/dynamic-extent.impure.lisp index be5ddbc..98d9966 100644 --- a/tests/dynamic-extent.impure.lisp +++ b/tests/dynamic-extent.impure.lisp @@ -557,7 +557,7 @@ ;; This fails on threaded PPC because the hash-table implementation ;; uses recursive system spinlocks, which cons (see below for test ;; (:no-consing :spinlock), which also fails on threaded PPC). -(with-test (:name (:no-consing :hash-tables) :fails-on (and :ppc :sb-thread)) +(with-test (:name (:no-consing :hash-tables) :fails-on '(and :ppc :sb-thread)) (assert-no-consing (test-hash-table))) ;;; with-spinlock and with-mutex should use DX and not cons diff --git a/version.lisp-expr b/version.lisp-expr index 36b238e..05f749e 100644 --- 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.42.25" +"1.0.42.26"