;;;; -*- coding: utf-8; fill-column: 78 -*-
changes relative to sbcl-1.0.34:
+ * optimization: SB-ROTATE-BYTE:ROTATE-BYTE now generates more efficient
+ code for 32-bit and 64-bit rotations on x86-64.
+ * bug fix: Passing a rotation count of zero to SB-ROTATE-BYTE:ROTATE-BYTE
+ no longer causes a compiler error on x86 and ppc.
* bug fix: GET-MACRO-CHARACTER bogusly computed its second return value
always relative to *READTABLE* rather than the passed argument.
(defknown %unsigned-32-rotate-byte ((integer -31 31) (unsigned-byte 32))
(unsigned-byte 32)
(foldable flushable))
+#+x86-64
+(defknown %unsigned-64-rotate-byte ((integer -63 63) (unsigned-byte 64))
+ (unsigned-byte 64)
+ (foldable flushable))
(macrolet (;; see src/compiler/srctran.lisp
(with-byte-specifier ((size-var pos-var spec) &body body)
*universal-type*)))
(deftransform %rotate-byte ((count size pos integer)
- ((constant-arg (member 0)) * * *) *)
- "fold identity operation"
- 'integer)
-
-(deftransform %rotate-byte ((count size pos integer)
((integer -31 31)
(constant-arg (member 32))
(constant-arg (member 0))
(unsigned-byte 32)) *)
"inline 32-bit rotation"
- ;; FIXME: What happens when, as here, the two type specifiers for
- ;; COUNT overlap? Which gets to run first?
'(%unsigned-32-rotate-byte count integer))
;; Generic implementation for platforms that don't supply VOPs for 32-bit
;; rotate.
-#-(or x86 ppc)
+#-(or x86 x86-64 ppc)
(deftransform %unsigned-32-rotate-byte ((.count. .integer.)
((integer -31 31)
(unsigned-byte 32)) *)
(ash .integer. .count.))
(logior (ldb (byte 32 0) (ash .integer. .count.))
(ash .integer. (- .count. 32)))))
+
+#+x86-64
+(deftransform %rotate-byte ((count size pos integer)
+ ((integer -63 63)
+ (constant-arg (member 64))
+ (constant-arg (member 0))
+ (unsigned-byte 64)) *)
+ "inline 64-bit rotation"
+ '(%unsigned-64-rotate-byte count integer))
+
+;;; This transform needs to come after the others to ensure it gets
+;;; first crack at a zero COUNT, since transforms are currently run
+;;; latest-defined first.
+(deftransform %rotate-byte ((count size pos integer)
+ ((constant-arg (member 0)) * * *) *)
+ "fold identity operation"
+ 'integer)
(in-package "SB-ROTATE-BYTE")
+;;; Ensure we don't bug out with an identity rotation.
+(assert (= (rotate-byte 0 (byte 32 0) 3) 3))
+
(assert (= (rotate-byte 3 (byte 32 0) 3) 24))
(assert (= (rotate-byte 3 (byte 16 0) 3) 24))
(assert (= (rotate-byte 3 (byte 2 0) 3) 3))
(assert (= (ub32-reg-pressure 5 5) 10880))
(assert (= (ub32-reg-pressure 5 (ash 1 26)) 2147494368))
(assert (= (ub32-reg-pressure 5 (ash 1 27)) 10721))
+
+(defun ub64/c (integer)
+ (declare (type (unsigned-byte 64) integer))
+ (rotate-byte 6 (byte 64 0) integer))
+
+(assert (= (ub64/c 5) 320))
+(assert (= (ub64/c 1) 64))
+(assert (= (ub64/c (ash 1 57)) (ash 1 63)))
+(assert (= (ub64/c (ash 1 58)) 1))
+
+(defun ub64 (count integer)
+ (declare (type (unsigned-byte 64) integer)
+ (type (integer -63 63) count))
+ (rotate-byte count (byte 64 0) integer))
+
+(assert (= (ub64 6 5) 320))
+(assert (= (ub64 6 1) 64))
+(assert (= (ub64 6 (ash 1 57)) (ash 1 63)))
+(assert (= (ub64 6 (ash 1 58)) 1))
:components
((:file "x86-vm"
:in-order-to ((compile-op (feature :x86))))
+ (:file "x86-64-vm"
+ :in-order-to ((compile-op (feature :x86-64))))
(:file "ppc-vm"
:in-order-to ((compile-op (feature :ppc)))))
:pathname
;;; 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.34.5"
+"1.0.34.6"