;;;; This file contains some parameterizations of various VM
;;;; attributes common to all architectures.

;;;; This software is part of the SBCL system. See the README file for
;;;; more information.
;;;;
;;;; This software is derived from the CMU CL system, which was
;;;; written at Carnegie Mellon University and released into the
;;;; public domain. The software is in the public domain and is
;;;; provided with absolutely no warranty. See the COPYING and CREDITS
;;;; files for more information.

(in-package "SB-VM")

;;; When building the cross-compiler (and called by the host), read the
;;; dynamic-space-size file.
;;; When called by the cross-compiler (in the host), use the previously chosen value.
;;; The target function is never called, but if omitted via #-sb-xc-host,
;;; compilation of !GENCGC-SPACE-SETUP would issue an "undefined" warning.
(defun !read-dynamic-space-size ()
  #+sb-xc-host
  (with-open-file (f "output/dynamic-space-size.txt" :if-does-not-exist nil)
    (unless f
      (return-from !read-dynamic-space-size nil))
    (let ((line (read-line f)))
      (multiple-value-bind (number end)
          (parse-integer line :junk-allowed t)
        (when number
            (let* ((ext (subseq line end))
                   (mult (cond ((or (zerop (length ext))
                                    (member ext '("MB" "MIB") :test #'equalp))
                                (expt 2 20))
                               ((member ext '("GB" "GIB") :test #'equalp)
                                (expt 2 30))
                               (t
                                (error "Invalid --dynamic-space-size=~A" line)))))
              (* number mult))))))
  #-sb-xc-host (symbol-value 'default-dynamic-space-size))

;; By happenstance this is the same as small-space-size.
(defconstant alien-linkage-table-space-size #x100000)

;; Define START/END constants for GC spaces.
;; Assumptions:
;;     We only need very small read-only and static spaces, because
;;     gencgc does not purify any more.  We can count on being able to
;;     allocate them with roughly the same size, and next to each other.
;;
;;     The linkage table (if enabled) can be treated the same way.
;;
;;     Dynamic space traditionally sits elsewhere, so has its own
;;     parameter.  But if not specified, it is allocated right after
;;     the other spaces (used on Windows/x86).
;;
;;     The safepoint page (if enabled) is to be allocated immediately
;;     prior to static page.
(defmacro gc-space-setup
    (small-spaces-start
          ;; These keywords variables have to be careful not to overlap with the
          ;; the DEFCONSTANT of the same name, hence the suffix.
          &key ((:dynamic-space-start dynamic-space-start*))
               ((:dynamic-space-size dynamic-space-size*))
               ;; The immobile-space START parameters should not be used
               ;; except in forcing discontiguous addresses for testing.
               ;; And of course, don't use them if unsupported.
               ((:fixedobj-space-start fixedobj-space-start*))
               ((:fixedobj-space-size  fixedobj-space-size*) (* 48 1024 1024))
               ((:text-space-start text-space-start*))
               ((:text-space-size  text-space-size*) (* 160 1024 1024))
               (small-space-size #x100000)
               ((:read-only-space-size ro-space-size)
                #+darwin-jit small-space-size
                #-darwin-jit 0))
  (declare (ignorable dynamic-space-start*)) ; might be unused in make-host-2
  (flet ((defconstantish (relocatable symbol value)
           (if (not relocatable) ; easy case
               `(defconstant ,symbol ,value)
               ;; Genesis needs to know the gspace start, but it's not constant.
               ;; This value will not be exposed to C code.
               #+sb-xc-host `(defparameter ,symbol ,value)
               ;; Ideally the #-sb-xc-host code be a DEFINE-ALIEN-VARIABLE,
               ;; but can't be due to dependency order problem.
               )))
    (let*
        ((spaces (append `((read-only ,ro-space-size)
                           #+(and win32 x86-64)
                           (seh-data ,(symbol-value '+backend-page-bytes+) win64-seh-data-addr)
                           #-immobile-space (alien-linkage-table ,alien-linkage-table-space-size)
                           ;; safepoint on 64-bit uses a relocatable trap page just below the card mark
                           ;; table, which works nicely assuming a register is wired to the card table
                           #+(and sb-safepoint (not x86-64))
                           ;; Must be just before NIL.
                           (safepoint ,(symbol-value '+backend-page-bytes+))
                           (static ,small-space-size)
                           (permgen 8388608) ; 8MiB
                           #+darwin-jit
                           (static-code ,small-space-size))
                         #+immobile-space
                         `((fixedobj ,fixedobj-space-size*)
                           (alien-linkage-table ,alien-linkage-table-space-size)
                           (text ,text-space-size*))))
         (ptr small-spaces-start)
         (small-space-forms
           (loop for (space size var-name) in spaces
                 appending
                 (let* ((relocatable
                          (member space '(fixedobj text permgen
                                          #+relocatable-static-space safepoint
                                          #+relocatable-static-space static
                                          #+immobile-space alien-linkage-table
                                          read-only)))
                        (start ptr)
                        (end (+ ptr size)))
                   (setf ptr end)
                   (if var-name
                       `((defconstant ,var-name ,start))
                       (let ((start-sym (symbolicate space "-SPACE-START")))
                         ;; Allow expressly given addresses / sizes for immobile space.
                         ;; The addresses are for testing only - you should not need them.
                         (case space
                           (text (setq start (or text-space-start* start)
                                       end (+ start text-space-size*)))
                           (fixedobj (setq start (or fixedobj-space-start* start)
                                           end (+ start fixedobj-space-size*))))
                         `(,(defconstantish relocatable start-sym start)
                           ,(cond ((eq space 'alien-linkage-table)) ; nothing for the -END
                                  ((not relocatable)
                                   `(defconstant ,(symbolicate space "-SPACE-END") ,end))
                                  #-sb-xc-host ((eq space 'text)) ; don't emit anything
                                  (t
                                   `(defconstant ,(symbolicate space "-SPACE-SIZE")
                                      ,(- end start)))))))))))
      `(progn
         ,@small-space-forms
         ,(defconstantish t 'dynamic-space-start
            (or dynamic-space-start* ptr))
         (defconstant default-dynamic-space-size
           ;; Build-time make-config.sh option "--dynamic-space-size" overrides
           ;; keyword argument :dynamic-space-size which overrides general default.
           ;; All are overridden by runtime --dynamic-space-size command-line arg.
           (or ,(or (!read-dynamic-space-size) dynamic-space-size*)
               (ecase n-word-bits
                 (32 (expt 2 29))
                 (64 (expt 2 30)))))
         ;; an arbitrary value to avoid kludging genesis
         #+sb-xc-host
         (defparameter read-only-space-end read-only-space-start)
         #-soft-card-marks (defconstant cards-per-page 1)
         (defconstant gencgc-card-bytes (/ gencgc-page-bytes cards-per-page))
         (defconstant gencgc-card-shift
           (integer-length (1- gencgc-card-bytes)))
         ;; This is a constant during build, but a different value
         ;; can be patched directly into the affected machine code
         ;; when the core is loaded based on dynamic-space-size.
         ;; I think the C runtime does a floor operation rather than ceiling,
         ;; but firstly there's probably no difference, and secondly it's better
         ;; to be safe than sorry - using too many bits rather than too few.
         (defconstant gencgc-card-table-index-nbits
           (integer-length (1- (ceiling default-dynamic-space-size
                                        gencgc-card-bytes))))
         (defconstant gencgc-card-table-index-mask
           (1- (ash 1 gencgc-card-table-index-nbits)))))))

(defconstant card-marked #+soft-card-marks 0 #-soft-card-marks 1)

(defconstant-eqx +c-callable-fdefns+
  '(sub-gc
    sb-kernel::post-gc
    internal-error
    sb-kernel::control-stack-exhausted-error
    sb-kernel::binding-stack-exhausted-error
    sb-kernel::alien-stack-exhausted-error
    sb-kernel::heap-exhausted-error
    sb-kernel::undefined-alien-variable-error
    sb-kernel::memory-fault-error
    sb-kernel::unhandled-trap-error
    ;; On these it's called through the internal errors mechanism
    #-(or arm arm64 x86-64) undefined-alien-fun-error
    sb-di::handle-breakpoint
    sb-di::handle-single-step-trap
    #+win32 sb-kernel::handle-win32-exception
    #+sb-safepoint sb-thread::run-interruption
    enter-alien-callback
    #+sb-thread sb-thread::enter-foreign-callback)
  #'equal)

;;; (potentially) static symbols that C code must be able to set/get
;;; as contrasted with static for other reasons such as:
;;;  - garbage collections roots (namely NIL)
;;;  - other symbols that Lisp codegen must hardwire (T)
;;;  - static for efficiency of access but need not be
;;; On #+sb-thread builds, these are not static, because access to them
;;; is via the TLS, not the symbol.
(defconstant-eqx per-thread-c-interface-symbols
    (hash-cons
     '((*free-interrupt-context-index* 0)
       (sb-sys:*allow-with-interrupts* t)
       (sb-sys:*interrupts-enabled* t)
       sb-sys:*interrupt-pending*
       #+sb-safepoint sb-sys:*thruption-pending*
       *in-without-gcing*
       *gc-inhibit*
       *gc-pending*
       #+sb-safepoint sb-impl::*in-safepoint*
       #+sb-thread *stop-for-gc-pending*
       sb-impl::*unweakened-vectors*
       *pinned-objects*
       (*gc-pin-code-pages* 0)
       ;; things needed for non-local-exit
       (*current-catch-block* 0)
       (*current-unwind-protect-block* 0)))
  #'equal)

(defconstant-eqx +common-static-symbols+
  `(t
    ;; These symbols are accessed from C only through TLS,
    ;; never the symbol-value slot
    #-sb-thread ,@(mapcar (lambda (x) (car (ensure-list x)))
                           per-thread-c-interface-symbols)
    ;; NLX variables are thread slots on x86-64 and RISC-V.  A static sym is needed
    ;; for arm64, ppc, and x86 because we haven't implemented TLS index fixups,
    ;; so must lookup the TLS index given the symbol.
    #+(and sb-thread (not x86-64) (not riscv))
    ,@'(*current-catch-block*
        *current-unwind-protect-block*)

    *immobile-codeblob-tree* ; for generations 0 through 5 inclusive
    *immobile-codeblob-vector* ; for pseudo-static-generation
    *dynspace-codeblob-tree*
    sb-impl::**finalizer-store**
    sb-impl::*finalizer-rehashlist*
    sb-impl::*finalizers-triggered*

    ;; stack pointers
    #-sb-thread *binding-stack-start* ; a thread slot if #+sb-thread
    #-sb-thread *control-stack-start* ; ditto
    #-sb-thread *control-stack-end*   ; ditto

    #-sb-thread *stepping*

    ;; threading support
    #+sb-thread sb-thread::*starting-threads*
    *free-tls-index* ; always exists for benefit of C runtime

    #+(and x86-64 sb-thread (not gs-seg))
    sb-aprof::*n-profile-sites*

    ;; runtime linking of lisp->C calls (regardless of whether
    ;; the C function is in a dynamic shared object or not)
    +required-foreign-symbols+

    ;;; The following symbols aren't strictly required to be static
    ;;; - they are not accessed from C - but we make them static in order
    ;;; to (perhaps) micro-optimize access in Lisp.
    ;;; However there is no efficiency gain if we have #+immobile-space.
    #-immobile-space ,@'(
     ;; arbitrary object that changes after each GC
     sb-kernel::*gc-epoch*
     ;; Dispatch tables for generic array access
     %%data-vector-reffers%%
     %%data-vector-reffers/check-bounds%%
     %%data-vector-setters%%
     %%data-vector-setters/check-bounds%%))
  #'equalp)

;;; Each backend must provide some 2-argument math routines as hand-written lisp
;;; assembly. Those routines punt to a lisp function for anything more complicated
;;; than fixnum inputs. To call lisp the general function, we need a fixed address
;;; holding its entry point, namely the static-fdefn. While we do allow boxed constants
;;; in the assembly code header now, it's not general enough for calling.
;;;
;;; Additionally, in the distant-but-memorable past there were things known
;;; as "static functions" which were essentially just vops that translated a few
;;; important functions such as LENGTH and %COERCE-CALLABLE-TO-FUN.
;;; (Surprisingly, LCM and GCD were deemed important enough to merit special status)
;;; The main purpose of a static function was to call it without reference to
;;; an #<fdefn>. But those "static functions" were unusual in that they bypassed
;;; the normal call convention. They were all deleted in the following change series:
;;;      d65b9573423610589319889a0eeb31c5501862bf Remove define-static-fun on MIPS.
;;;      f39d1846e90ed20cd529ce2fb701de9ad0293f59 Remove define-static-fun on SPARC.
;;;      1c190e01a08481440c420c7bb8db5c1800775c01 Remove define-static-fun on ARM.
;;;      87ae85c665aa1d6c710293632bee495619e5ed62 Remove define-static-fun on PPC.
;;;      e3c05bb0b955ef41c3b920d151606f195d17d89e Remove define-static-fun on x86.
;;;      eb210dc031710a35b0ef4f39b775e7960f710790 Remove define-static-fun on ARM64.
;;;      a8e9e678fb8ef2777d45afb1a8cce93277d44df6 Get rid of define-static-fun on x86-64.
;;; The corresponding static-fdefns should have been deleted with them.
;;;
;;; However, it is still true that some functions are of such importance
;;; that calling them with 1 fewer instruction and 1 fewer code header constant
;;; yields measurable space savings. e.g. TWO-ARG-LCM had almost no callers
;;; so there's no reason to think it's important.
#|
(let ((table (make-hash-table)))
  (dolist (c (sb-vm:list-allocated-objects :all :type sb-vm:code-header-widetag))
    (multiple-value-bind (start count) (sb-kernel:code-header-fdefn-range c)
      (loop for i from start repeat count
            do (let ((const (sb-kernel:code-header-ref c i)))
                 (incf (gethash const table 0))))))
  (dolist (x (sort (sb-int:%hash-table-alist table) #'> :key #'cdr))
    (format t "~5d ~s~%" (cdr x) (car x))))
|#

(defconstant-eqx common-static-fdefns
    '(;; This the standard set of assembly routines that need to call into lisp.
      ;; A few backends add TWO-ARG-/= and others to this, in their {arch}/parms
      two-arg-+
      two-arg--
      two-arg-*
      two-arg-/
      two-arg-<
      two-arg->
      two-arg-=
      eql
      %negate
      ;; These next ones are not called from assembly code, but from lisp.
      length
      error
      format
      equalp
      sb-c::check-ds-list
      sb-c::check-ds-list/&rest
      write-string
      write-char
      princ
      ;; A scientific but cursory examination of one particular application
      ;; revealed that the most popular functions to be referenced from any other
      ;; are the hairy vector accessors. Those two alone accounted for 18% of all
      ;; fdefn pointers in the core. A couple others were high on the list as well.
      hairy-data-vector-set
      hairy-data-vector-ref
      vector-hairy-data-vector-set
      vector-hairy-data-vector-ref
      hairy-data-vector-set/check-bounds
      hairy-data-vector-ref/check-bounds
      vector-hairy-data-vector-set/check-bounds
      vector-hairy-data-vector-ref/check-bounds
      %ldb
      sb-kernel:vector-unsigned-byte-8-p)
  #'equalp)

;;; Refer to the lengthy comment in 'src/runtime/interrupt.h' about
;;; the choice of this number. Rather than have to two copies
;;; of the comment, please see that file before adjusting this.
;;; I think most of the need for a ridiculously large value stemmed from
;;; receive-pending-interrupt after a pseudo-atomic code section.
;;; If that trapped into GC, and then ran finalizers in POST-GC (while still
;;; in a signal handler), which consed, which caused the need for another GC,
;;; you'd receive a nested interrupt, as the GC trap was still on the stack
;;; not having returned to "user" code yet. [See example in src/code/final]
;;;
;;; But now that #+sb-thread creates a dedicated finalizer thread, nesting
;;; seems unlikely to occur, because "your" code doesn't get a chance to run again
;;; until after the interrupt returns. And the finalizer thread won't invoke
;;; run-pending-finalizers in post-GC, it will just pick up the next finalizer
;;; in due turn. You could potentially force a nested GC by consing a lot in
;;; a post-GC hook, but if you do that, your hook function is badly behaved
;;; and you should fix it.
(defconstant max-interrupts
  #+sb-thread    8  ; reasonable value
  #-sb-thread 1024) ; crazy value

;;; Thread slots accessed at negative indices relative to struct thread.
;;; FIXME: this is extremely unmaintainable.
(defconstant thread-header-slots
  ;; This seems to need to be an even number.
  ;; I'm not sure what the constraint on that stems from.
  #+(and x86-64 sb-safepoint) 14 ; the safepoint trap page is at word index -15
  #+(and x86-64 (not sb-safepoint)) 16
  #+(and (not x86-64) immobile-space) 14 ; the safepoint trap page is at word index -15
  #+(and (not x86-64) (not immobile-space)) 0)

(progn
  (defconstant +highest-normal-generation+ 5)
  (defconstant +pseudo-static-generation+ 6))

(defparameter *runtime-asm-routines* nil)
(defparameter *alien-linkage-table-predefined-entries* nil)

;;; Floating-point related constants, both format descriptions and FPU
;;; control register descriptions.  These don't exactly match up with
;;; what the machine manuals say because the Common Lisp standard
;;; defines floating-point values somewhat differently than the IEEE
;;; standard does.

;;; We can currently manipulate only IEEE single and double precision.
;;; Machine-specific formats (such as x86 80-bit and PPC double-double)
;;; are unsupported.

#+ieee-floating-point
(progn
(defconstant float-sign-shift 31)

;;; The exponent bias is the amount up by which the true exponent is
;;; incremented for storage purposes.
;;; (Wikipedia entry for single-float: "an exponent value of 127 represents the actual zero")
;;; 126 works for us because we actually want an exponent of -1 and not 0
;;; when using DECODE-FLOAT. -1 is correct because the implied 1 bit in a normalized
;;; float is the _left_ of of the binary point, so the powers of 2 for the first represented
;;; bit is 2^-1. Similarly for double-float.
(defconstant single-float-bias 126)
(defconstant-eqx single-float-exponent-byte (byte 8 23) #'equalp)
(defconstant-eqx single-float-significand-byte (byte 23 0) #'equalp)
(defconstant single-float-normal-exponent-min 1)
(defconstant single-float-normal-exponent-max 254)
(defconstant single-float-hidden-bit (ash 1 23))

(defconstant double-float-bias 1022)
(defconstant-eqx double-float-exponent-byte (byte 11 52) #'equalp)
(defconstant-eqx double-float-significand-byte (byte 52 0) #'equalp)
(defconstant-eqx double-float-hi-exponent-byte (byte 11 20) #'equalp)
(defconstant-eqx double-float-hi-significand-byte (byte 20 0) #'equalp)
(defconstant double-float-normal-exponent-min 1)
(defconstant double-float-normal-exponent-max #x7FE)
(defconstant double-float-hidden-bit (ash 1 52))

(defconstant single-float-digits 24)
(defconstant double-float-digits 53)
)

(push '("SB-VM" +c-callable-fdefns+ +common-static-symbols+)
      *!removable-symbols*)
