;;; addressable object
(def!constant n-byte-bits 8)
+;;; The size in bytes of the GENCGC pages. Should be a multiple of the
+;;; architecture code size.
+(def!constant gencgc-page-size 4096)
+
(def!constant float-sign-shift 31)
;;; comment from CMU CL:
;;; These values were taken from the alpha code. The values for
;;; bias and exponent min/max are not the same as shown in the 486 book.
;;; They may be correct for how Python uses them.
-(def!constant single-float-bias 126) ; Intel says 127.
+(def!constant single-float-bias 126) ; Intel says 127.
(defconstant-eqx single-float-exponent-byte (byte 8 23) #'equalp)
(defconstant-eqx single-float-significand-byte (byte 23 0) #'equalp)
;;; comment from CMU CL:
(def!constant double-float-hidden-bit (ash 1 20))
(def!constant double-float-trapping-nan-bit (ash 1 19))
-(def!constant long-float-bias 16382)
-(defconstant-eqx long-float-exponent-byte (byte 15 0) #'equalp)
-(defconstant-eqx long-float-significand-byte (byte 31 0) #'equalp)
-(def!constant long-float-normal-exponent-min 1)
-(def!constant long-float-normal-exponent-max #x7FFE)
-(def!constant long-float-hidden-bit (ash 1 31)) ; actually not hidden
-(def!constant long-float-trapping-nan-bit (ash 1 30))
-
(def!constant single-float-digits
(+ (byte-size single-float-significand-byte) 1))
(def!constant double-float-digits
(+ (byte-size double-float-significand-byte) 32 1))
-(def!constant long-float-digits
- (+ (byte-size long-float-significand-byte) 32 1))
-
-;;; pfw -- from i486 microprocessor programmer's reference manual
-(def!constant float-invalid-trap-bit (ash 1 0))
+;;; from AMD64 Architecture manual
+(def!constant float-invalid-trap-bit (ash 1 0))
(def!constant float-denormal-trap-bit (ash 1 1))
(def!constant float-divide-by-zero-trap-bit (ash 1 2))
(def!constant float-overflow-trap-bit (ash 1 3))
(def!constant float-underflow-trap-bit (ash 1 4))
-(def!constant float-inexact-trap-bit (ash 1 5))
+(def!constant float-inexact-trap-bit (ash 1 5))
(def!constant float-round-to-nearest 0)
(def!constant float-round-to-negative 1)
(def!constant float-round-to-positive 2)
(def!constant float-round-to-zero 3)
-(defconstant-eqx float-rounding-mode (byte 2 10) #'equalp)
-(defconstant-eqx float-sticky-bits (byte 6 16) #'equalp)
-(defconstant-eqx float-traps-byte (byte 6 0) #'equalp)
-(defconstant-eqx float-exceptions-byte (byte 6 16) #'equalp)
-(defconstant-eqx float-precision-control (byte 2 8) #'equalp)
-(def!constant float-fast-bit 0) ; no fast mode on x86
+(defconstant-eqx float-rounding-mode (byte 2 13) #'equalp)
+(defconstant-eqx float-sticky-bits (byte 6 0) #'equalp)
+(defconstant-eqx float-traps-byte (byte 6 7) #'equalp)
+(defconstant-eqx float-exceptions-byte (byte 6 0) #'equalp)
+(def!constant float-fast-bit 0) ; no fast mode on x86-64
\f
;;;; description of the target address space
-;;; where to put the different spaces. untested (copied from x86, in fact)
+;;; where to put the different spaces.
+;;; Currently the read-only and static spaces must be located in low
+;;; memory (certainly under the 4GB limit, very probably under 2GB
+;;; limit). This is due to the inability of using immediate values of
+;;; more than 32 bits (31 bits if you take sign extension into
+;;; account) in any other instructions except MOV. Removing this limit
+;;; would be possible, but probably not worth the time and code bloat
+;;; it would cause. -- JES, 2005-12-11
-(def!constant read-only-space-start #x01000000)
-(def!constant read-only-space-end #x037ff000)
+(def!constant read-only-space-start #x20000000)
+(def!constant read-only-space-end #x27ff0000)
-(def!constant static-space-start #x05000000)
-(def!constant static-space-end #x07fff000)
+(def!constant static-space-start #x40000000)
+(def!constant static-space-end #x47fff000)
-(def!constant dynamic-space-start #x09000000)
-(def!constant dynamic-space-end #x29000000)
+(def!constant dynamic-space-start #x1000000000)
+(def!constant dynamic-space-end #x11ffff0000)
+(def!constant linkage-table-space-start #x60000000)
+(def!constant linkage-table-space-end #x63fff000)
+
+(def!constant linkage-table-entry-size 16)
\f
;;;; other miscellaneous constants
(defvar *allocation-pointer*)
(defvar *binding-stack-pointer*)
-;;; FIXME: !COLD-INIT probably doesn't need
-;;; to be in the static symbols table any more.
(defparameter *static-symbols*
- '(t
-
- ;; The C startup code must fill these in.
- *posix-argv*
-
- ;; functions that the C code needs to call. When adding to this list,
- ;; also add a `frob' form in genesis.lisp finish-symbols.
- sub-gc
- sb!kernel::internal-error
- sb!kernel::control-stack-exhausted-error
- sb!di::handle-breakpoint
- fdefinition-object
- #!+sb-thread sb!thread::handle-thread-exit
-
- ;; free pointers
- ;;
- ;; Note that these are FIXNUM word counts, not (as one might
- ;; expect) byte counts or SAPs. The reason seems to be that by
- ;; representing them this way, we can avoid consing bignums.
- ;; -- WHN 2000-10-02
- *read-only-space-free-pointer*
- *static-space-free-pointer*
- *initial-dynamic-space-free-pointer*
-
- ;; things needed for non-local exit
- *current-catch-block*
- *current-unwind-protect-block*
- *alien-stack*
-
- ;; interrupt handling
- *pseudo-atomic-atomic*
- *pseudo-atomic-interrupted*
- sb!unix::*interrupts-enabled*
- sb!unix::*interrupt-pending*
- *free-interrupt-context-index*
-
- *free-tls-index*
-
- *allocation-pointer*
- *binding-stack-pointer*
- *binding-stack-start*
- *control-stack-start*
- *control-stack-end*
-
- ;; the floating point constants
- *fp-constant-0d0*
- *fp-constant-1d0*
- *fp-constant-0f0*
- *fp-constant-1f0*
- ;; The following are all long-floats.
- *fp-constant-0l0*
- *fp-constant-1l0*
- *fp-constant-pi*
- *fp-constant-l2t*
- *fp-constant-l2e*
- *fp-constant-lg2*
- *fp-constant-ln2*
-
- ;; The ..SLOT-UNBOUND.. symbol is static in order to optimise the
- ;; common slot unbound check.
- ;;
- ;; FIXME: In SBCL, the CLOS code has become sufficiently tightly
- ;; integrated into the system that it'd probably make sense to use
- ;; the ordinary unbound marker for this.
- sb!pcl::..slot-unbound..))
+ (append
+ *common-static-symbols*
+ *c-callable-static-symbols*
+ '(*alien-stack*
+
+ ;; interrupt handling
+ *pseudo-atomic-bits*
+
+ #!+sb-thread *stop-for-gc-pending*
+
+ #!+sb-thread *free-tls-index*
+ #!+sb-thread *tls-index-lock*
+
+ *allocation-pointer*
+ *binding-stack-pointer*
+
+ ;; the floating point constants
+ *fp-constant-0d0*
+ *fp-constant-1d0*
+ *fp-constant-0f0*
+ *fp-constant-1f0*
+
+ ;; For GC-AND-SAVE
+ *restart-lisp-function*
+
+ ;; Needed for callbacks to work across saving cores. see
+ ;; ALIEN-CALLBACK-ASSEMBLER-WRAPPER in c-call.lisp for gory
+ ;; details.
+ sb!alien::*enter-alien-callback*
+
+ ;; The ..SLOT-UNBOUND.. symbol is static in order to optimise the
+ ;; common slot unbound check.
+ ;;
+ ;; FIXME: In SBCL, the CLOS code has become sufficiently tightly
+ ;; integrated into the system that it'd probably make sense to
+ ;; use the ordinary unbound marker for this.
+ ;;
+ ;; FIXME II: if it doesn't make sense, why is this X86-ish only?
+ sb!pcl::..slot-unbound..)))
(defparameter *static-funs*
'(length
sb!kernel:two-arg-xor
sb!kernel:two-arg-gcd
sb!kernel:two-arg-lcm))
-\f
-;;;; stuff added by jrd
-
-;;; FIXME: Is this used? Delete it or document it.
-;;; cf the sparc PARMS.LISP
-(defparameter *assembly-unit-length* 8)
projects / sbcl.git / blobdiff