X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcompiler%2Fx86-64%2Fparms.lisp;h=eed4cfedf030a2583f54d26742ea3bd952ced652;hb=a4882e3023fdd5e777169a4cbede33605281173c;hp=f80bbf2e3fbf88f546f34048880513facdf973a4;hpb=939275c1bc2f18ef93cd1dd4ab35a18f6008cfd9;p=sbcl.git diff --git a/src/compiler/x86-64/parms.lisp b/src/compiler/x86-64/parms.lisp index f80bbf2..eed4cfe 100644 --- a/src/compiler/x86-64/parms.lisp +++ b/src/compiler/x86-64/parms.lisp @@ -35,6 +35,10 @@ ;;; 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: @@ -89,6 +93,14 @@ ;;; 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 #x20000000) (def!constant read-only-space-end #x27ff0000) @@ -147,75 +159,47 @@ (defvar *allocation-pointer*) (defvar *binding-stack-pointer*) -;;; FIXME: !COLD-INIT probably doesn't need -;;; to be in the static symbols table any more. -;;; -;;; FIXME: some of these symbols are shared by all backends, -;;; and should be factored out into a common file. (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!kernel::undefined-alien-variable-error - sb!kernel::undefined-alien-function-error - sb!kernel::memory-fault-error - sb!di::handle-breakpoint - fdefinition-object - - ;; 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* - *gc-inhibit* - #!+sb-thread *stop-for-gc-pending* - *gc-pending* - - *free-tls-index* - *tls-index-lock* - - *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 ..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-atomic* + *pseudo-atomic-interrupted* + + #!+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