X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcompiler%2Fearly-assem.lisp;h=317b100981e94f0c40b4af4d06d886ac0d0384bc;hb=7f1e94ae961a198e00daf281eb1dc858e5b2dcc7;hp=0162a0c9724f16754dcaaac284992148d48f1492;hpb=cea4896b2482b7b2b429c1631d774b4cfbc0efba;p=sbcl.git

diff --git a/src/compiler/early-assem.lisp b/src/compiler/early-assem.lisp
index 0162a0c..317b100 100644
--- a/src/compiler/early-assem.lisp
+++ b/src/compiler/early-assem.lisp
@@ -26,26 +26,26 @@
 ;;; 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 ()
+(def!type assembly-unit ()
   `(unsigned-byte ,assembly-unit-bits))
 
 ;;; Some functions which accept assembly units can meaningfully accept
 ;;; signed values with the same number of bits and silently munge them
 ;;; into appropriate unsigned values. (This is handy behavior e.g.
 ;;; when assembling branch instructions on the X86.)
-(deftype possibly-signed-assembly-unit ()
+(def!type possibly-signed-assembly-unit ()
   `(or assembly-unit
        (signed-byte ,assembly-unit-bits)))
 
 ;;; 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 sb!vm:n-lowtag-bits)
 
-(deftype alignment ()
+(def!type alignment ()
   `(integer 0 ,max-alignment))