X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Fcross-float.lisp;h=b6c4ff1517f427335ebcd6048d19920d4be254e7;hb=4fc9d21ae1d8a6a2f8ff70f589d5da103203de13;hp=a820745b8237a988f1de07d7591749c0f5f3c0b7;hpb=cea4896b2482b7b2b429c1631d774b4cfbc0efba;p=sbcl.git

diff --git a/src/code/cross-float.lisp b/src/code/cross-float.lisp
index a820745..b6c4ff1 100644
--- a/src/code/cross-float.lisp
+++ b/src/code/cross-float.lisp
@@ -13,9 +13,9 @@
 
 (in-package "SB!IMPL")
 
-;;; There seems to be no portable way to mask float traps, but we shouldn't
-;;; encounter any float traps when cross-compiling SBCL itself, anyway, so we
-;;; just make this a no-op.
+;;; There seems to be no portable way to mask float traps, but we
+;;; shouldn't encounter any float traps when cross-compiling SBCL
+;;; itself, anyway, so we just make this a no-op.
 (defmacro sb!vm::with-float-traps-masked (traps &body body)
   (declare (ignore traps))
   ;; FIXME: should become STYLE-WARNING?
@@ -36,8 +36,8 @@
       (logior uresult
 	      (logand -1 (lognot mask))))))
 
-;;; portable implementations of SINGLE-FLOAT-BITS, DOUBLE-FLOAT-LOW-BITS, and
-;;; DOUBLE-FLOAT-HIGH-BITS
+;;; portable implementations of SINGLE-FLOAT-BITS,
+;;; DOUBLE-FLOAT-LOW-BITS, and DOUBLE-FLOAT-HIGH-BITS
 ;;;
 ;;; KLUDGE: These will fail if the target's floating point isn't IEEE, and so
 ;;; I'd be more comfortable if there were an assertion "target's floating point
@@ -79,7 +79,7 @@
 			 (>= significand (expt 2 23))
 			 (assert (< 0 significand (expt 2 24)))
 			 ;; Exponent 0 is reserved for denormalized numbers,
-			 ;; and 255 is reserved for specials a la NaN.
+			 ;; and 255 is reserved for specials like NaN.
 			 (assert (< 0 exponent 255))
 			 (return (logior (ash exponent 23)
 					 (logand significand
@@ -124,7 +124,7 @@
 			 (>= significand (expt 2 52))
 			 (assert (< 0 significand (expt 2 53)))
 			 ;; Exponent 0 is reserved for denormalized numbers,
-			 ;; and 2047 is reserved for specials a la NaN.
+			 ;; and 2047 is reserved for specials like NaN.
 			 (assert (< 0 exponent 2047))
 			 (return (logior (ash exponent 52)
 					 (logand significand
@@ -171,7 +171,7 @@
 ;;; cross-compilation host Lisps are likely to have exactly the same
 ;;; floating point precision as the target Lisp. If it turns out to be
 ;;; a problem, there are possible workarounds involving portable
-;;; representations for target floating point numbers, a la
+;;; representations for target floating point numbers, like
 ;;;   (DEFSTRUCT TARGET-SINGLE-FLOAT
 ;;;     (SIGN (REQUIRED-ARGUMENT) :TYPE BIT)
 ;;;     (EXPONENT (REQUIRED-ARGUMENT) :TYPE UNSIGNED-BYTE)