0.8.0.59:

[sbcl.git] / src / compiler / early-assem.lisp

diff --git a/src/compiler/early-assem.lisp b/src/compiler/early-assem.lisp
index 62f3561..13e756a 100644 (file)
--- a/src/compiler/early-assem.lisp
+++ b/src/compiler/early-assem.lisp
@@ -11,9 +11,6 @@
 
 (in-package "SB!ASSEM")
 
-(sb!int:file-comment
-  "$Header$")
-
 ;;; FIXME: It might make sense to use SB!VM:BYTE-FOO values here
 ;;; instead of the various ASSEMBLY-UNIT-FOO things, and then define a
 ;;; BYTE type. One problem: BYTE is exported from the CL package, so
@@ -29,10 +26,10 @@
 ;;; sequence.)
 
 ;;; ASSEMBLY-UNIT-BITS -- the number of bits in the minimum assembly
-;;; unit, (also refered to as a ``byte''). Hopefully, different
+;;; unit, (also referred to as a ``byte''). Hopefully, different
 ;;; instruction sets won't require changing this.
-(defconstant assembly-unit-bits 8)
-(defconstant assembly-unit-mask (1- (ash 1 assembly-unit-bits)))
+(def!constant assembly-unit-bits 8)
+(def!constant assembly-unit-mask (1- (ash 1 assembly-unit-bits)))
 
 (deftype assembly-unit ()
   `(unsigned-byte ,assembly-unit-bits))
@@ -48,7 +45,7 @@
 ;;; the maximum alignment we can guarantee given the object format. If
 ;;; the loader only loads objects 8-byte aligned, we can't do any
 ;;; better then that ourselves.
-(defconstant max-alignment 3)
+(def!constant max-alignment 3)
 
 (deftype alignment ()
   `(integer 0 ,max-alignment))