From 82d3524fd69a6a663c59ad2af4693a872e58ca0d Mon Sep 17 00:00:00 2001 From: Thiemo Seufer Date: Wed, 5 Sep 2007 20:36:10 +0000 Subject: [PATCH] 1.0.9.36: Match the correct atomicity bit. The wonders of copy & paste ... --- src/compiler/mips/macros.lisp | 3 +-- version.lisp-expr | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/src/compiler/mips/macros.lisp b/src/compiler/mips/macros.lisp index 44d87ca41..1598bc6c8 100644 --- a/src/compiler/mips/macros.lisp +++ b/src/compiler/mips/macros.lisp @@ -172,8 +172,7 @@ placed inside the PSEUDO-ATOMIC, and presumably initializes the object." ;; has a 1 bit in the same position, we're all set. Otherwise, ;; we need to subtract the pseudo-atomic bit. (inst or ,result-tn alloc-tn ,lowtag) - (unless (logbitp (1- n-lowtag-bits) ,lowtag) - (inst sub ,result-tn 1)) + (unless (logbitp 0 ,lowtag) (inst sub ,result-tn 1)) (inst li ,temp-tn (logior (ash (1- ,size) n-widetag-bits) ,type-code)) (storew ,temp-tn ,result-tn 0 ,lowtag) ,@body)))) diff --git a/version.lisp-expr b/version.lisp-expr index 27a6b8fb3..604073b99 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.9.35" +"1.0.9.36" -- 2.11.4.GIT