X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcompiler%2Fx86-64%2Fparms.lisp;h=8d14f7eb1e728577f46c323575ba0b0a2ae976ba;hb=0e3c4b4db102bd204a30402d7e5a0de44aea57ce;hp=2afd891e61abefdda6f391a564ac1eca590011b3;hpb=93be0089fe7b2a9e34bf1cb6da9fe6e902769f5e;p=sbcl.git diff --git a/src/compiler/x86-64/parms.lisp b/src/compiler/x86-64/parms.lisp index 2afd891..8d14f7e 100644 --- a/src/compiler/x86-64/parms.lisp +++ b/src/compiler/x86-64/parms.lisp @@ -20,7 +20,7 @@ ;;; and register specs, we use the Intel convention. But whenever we ;;; are talking about stuff the rest of the lisp system might be ;;; interested in, we use ``word'' to mean the size of a descriptor -;;; object, which is 32 bits. +;;; object, which is 64 bits. ;;;; machine architecture parameters @@ -35,9 +35,11 @@ ;;; 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) +;;; The minimum immediate offset in a memory-referencing instruction. +(def!constant minimum-immediate-offset (- (expt 2 31))) + +;;; The maximum immediate offset in a memory-referencing instruction. +(def!constant maximum-immediate-offset (1- (expt 2 31))) (def!constant float-sign-shift 31) @@ -101,47 +103,38 @@ ;;; 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) +;;; The default dynamic space size is lower on OpenBSD to allow SBCL to +;;; run under the default 512M data size limit. -(def!constant static-space-start #x40000000) -(def!constant static-space-end #x47fff000) +(!gencgc-space-setup #x20000000 + #x1000000000 -(def!constant dynamic-space-start #x1000000000) -(def!constant dynamic-space-end #x11ffff0000) + ;; :default-dynamic-space-size + #!+openbsd #x1bcf0000 -(def!constant linkage-table-space-start #x60000000) -(def!constant linkage-table-space-end #x63fff000) + ;; :alignment + #!+win32 #!+win32 nil #x10000) (def!constant linkage-table-entry-size 16) + ;;;; other miscellaneous constants -(defenum (:suffix -trap :start 8) - halt - pending-interrupt - error - cerror - breakpoint - fun-end-breakpoint - single-step-breakpoint) -;;; FIXME: It'd be nice to replace all the DEFENUMs with something like -;;; (WITH-DEF-ENUM (:START 8) -;;; (DEF-ENUM HALT-TRAP) -;;; (DEF-ENUM PENDING-INTERRUPT-TRAP) -;;; ..) -;;; for the benefit of anyone doing a lexical search for definitions -;;; of these symbols. - -(defenum (:prefix object-not- :suffix -trap :start 16) - list - instance) - -(defenum (:prefix trace-table-) - normal - call-site - fun-prologue - fun-epilogue) +(defenum (:start 8) + halt-trap + pending-interrupt-trap + error-trap + cerror-trap + breakpoint-trap + fun-end-breakpoint-trap + single-step-around-trap + single-step-before-trap) + +(defenum (:start 24) + object-not-list-trap + object-not-instance-trap + #!+sb-safepoint global-safepoint-trap + #!+sb-safepoint csp-safepoint-trap) ;;;; static symbols @@ -159,83 +152,41 @@ (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* - #!+sb-thread sb!thread::run-interruption - - *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* - - ;; 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. - sb!pcl::..slot-unbound..)) + (append + *common-static-symbols* + *c-callable-static-symbols* + '(*alien-stack* + + ;; interrupt handling + *pseudo-atomic-bits* + + *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 @@ -252,4 +203,8 @@ sb!kernel:two-arg-ior sb!kernel:two-arg-xor sb!kernel:two-arg-gcd - sb!kernel:two-arg-lcm)) + sb!kernel:two-arg-lcm + sb!kernel:%coerce-callable-to-fun)) + +#!+sb-simd-pack +(defvar *simd-pack-element-types* '(integer single-float double-float))