1.0.1.28: Fix SBCL on PPC with 65k pages.
[sbcl.git] / src / compiler / x86-64 / parms.lisp
blob0249f13b8d248a6d735e2e24c8423cde974069d9
1 ;;;; This file contains some parameterizations of various VM
2 ;;;; attributes for the x86. This file is separate from other stuff so
3 ;;;; that it can be compiled and loaded earlier.
5 ;;;; This software is part of the SBCL system. See the README file for
6 ;;;; more information.
7 ;;;;
8 ;;;; This software is derived from the CMU CL system, which was
9 ;;;; written at Carnegie Mellon University and released into the
10 ;;;; public domain. The software is in the public domain and is
11 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
12 ;;;; files for more information.
14 (in-package "SB!VM")
16 ;;; ### Note: we simultaneously use ``word'' to mean a 32 bit quantity
17 ;;; and a 16 bit quantity depending on context. This is because Intel
18 ;;; insists on calling 16 bit things words and 32 bit things
19 ;;; double-words (or dwords). Therefore, in the instruction definition
20 ;;; and register specs, we use the Intel convention. But whenever we
21 ;;; are talking about stuff the rest of the lisp system might be
22 ;;; interested in, we use ``word'' to mean the size of a descriptor
23 ;;; object, which is 32 bits.
25 ;;;; machine architecture parameters
27 ;;; the number of bits per word, where a word holds one lisp descriptor
28 (def!constant n-word-bits 64)
30 ;;; the natural width of a machine word (as seen in e.g. register width,
31 ;;; address space)
32 (def!constant n-machine-word-bits 64)
34 ;;; the number of bits per byte, where a byte is the smallest
35 ;;; addressable object
36 (def!constant n-byte-bits 8)
38 (def!constant float-sign-shift 31)
40 ;;; comment from CMU CL:
41 ;;; These values were taken from the alpha code. The values for
42 ;;; bias and exponent min/max are not the same as shown in the 486 book.
43 ;;; They may be correct for how Python uses them.
44 (def!constant single-float-bias 126) ; Intel says 127.
45 (defconstant-eqx single-float-exponent-byte (byte 8 23) #'equalp)
46 (defconstant-eqx single-float-significand-byte (byte 23 0) #'equalp)
47 ;;; comment from CMU CL:
48 ;;; The 486 book shows the exponent range -126 to +127. The Lisp
49 ;;; code that uses these values seems to want already biased numbers.
50 (def!constant single-float-normal-exponent-min 1)
51 (def!constant single-float-normal-exponent-max 254)
52 (def!constant single-float-hidden-bit (ash 1 23))
53 (def!constant single-float-trapping-nan-bit (ash 1 22))
55 (def!constant double-float-bias 1022)
56 (defconstant-eqx double-float-exponent-byte (byte 11 20) #'equalp)
57 (defconstant-eqx double-float-significand-byte (byte 20 0) #'equalp)
58 (def!constant double-float-normal-exponent-min 1)
59 (def!constant double-float-normal-exponent-max #x7FE)
60 (def!constant double-float-hidden-bit (ash 1 20))
61 (def!constant double-float-trapping-nan-bit (ash 1 19))
63 (def!constant single-float-digits
64 (+ (byte-size single-float-significand-byte) 1))
66 (def!constant double-float-digits
67 (+ (byte-size double-float-significand-byte) 32 1))
69 ;;; from AMD64 Architecture manual
70 (def!constant float-invalid-trap-bit (ash 1 0))
71 (def!constant float-denormal-trap-bit (ash 1 1))
72 (def!constant float-divide-by-zero-trap-bit (ash 1 2))
73 (def!constant float-overflow-trap-bit (ash 1 3))
74 (def!constant float-underflow-trap-bit (ash 1 4))
75 (def!constant float-inexact-trap-bit (ash 1 5))
77 (def!constant float-round-to-nearest 0)
78 (def!constant float-round-to-negative 1)
79 (def!constant float-round-to-positive 2)
80 (def!constant float-round-to-zero 3)
82 (defconstant-eqx float-rounding-mode (byte 2 13) #'equalp)
83 (defconstant-eqx float-sticky-bits (byte 6 0) #'equalp)
84 (defconstant-eqx float-traps-byte (byte 6 7) #'equalp)
85 (defconstant-eqx float-exceptions-byte (byte 6 0) #'equalp)
86 (def!constant float-fast-bit 0) ; no fast mode on x86-64
88 ;;;; description of the target address space
90 ;;; where to put the different spaces.
92 ;;; Currently the read-only and static spaces must be located in low
93 ;;; memory (certainly under the 4GB limit, very probably under 2GB
94 ;;; limit). This is due to the inability of using immediate values of
95 ;;; more than 32 bits (31 bits if you take sign extension into
96 ;;; account) in any other instructions except MOV. Removing this limit
97 ;;; would be possible, but probably not worth the time and code bloat
98 ;;; it would cause. -- JES, 2005-12-11
100 (def!constant read-only-space-start #x20000000)
101 (def!constant read-only-space-end #x27ff0000)
103 (def!constant static-space-start #x40000000)
104 (def!constant static-space-end #x47fff000)
106 (def!constant dynamic-space-start #x1000000000)
107 (def!constant dynamic-space-end #x11ffff0000)
109 (def!constant linkage-table-space-start #x60000000)
110 (def!constant linkage-table-space-end #x63fff000)
112 (def!constant linkage-table-entry-size 16)
114 ;;;; other miscellaneous constants
116 (defenum (:suffix -trap :start 8)
117 halt
118 pending-interrupt
119 error
120 cerror
121 breakpoint
122 fun-end-breakpoint
123 single-step-around
124 single-step-before)
125 ;;; FIXME: It'd be nice to replace all the DEFENUMs with something like
126 ;;; (WITH-DEF-ENUM (:START 8)
127 ;;; (DEF-ENUM HALT-TRAP)
128 ;;; (DEF-ENUM PENDING-INTERRUPT-TRAP)
129 ;;; ..)
130 ;;; for the benefit of anyone doing a lexical search for definitions
131 ;;; of these symbols.
133 (defenum (:prefix object-not- :suffix -trap :start 24)
134 list
135 instance)
137 (defenum (:prefix trace-table-)
138 normal
139 call-site
140 fun-prologue
141 fun-epilogue)
143 ;;;; static symbols
145 ;;; These symbols are loaded into static space directly after NIL so
146 ;;; that the system can compute their address by adding a constant
147 ;;; amount to NIL.
149 ;;; The fdefn objects for the static functions are loaded into static
150 ;;; space directly after the static symbols. That way, the raw-addr
151 ;;; can be loaded directly out of them by indirecting relative to NIL.
153 ;;; we could profitably keep these in registers on x86-64 now we have
154 ;;; r8-r15 as well
155 ;;; Note these spaces grow from low to high addresses.
156 (defvar *allocation-pointer*)
157 (defvar *binding-stack-pointer*)
159 (defparameter *static-symbols*
160 (append
161 *common-static-symbols*
162 *c-callable-static-symbols*
163 '(*alien-stack*
165 ;; interrupt handling
166 *pseudo-atomic-bits*
168 #!+sb-thread *stop-for-gc-pending*
170 #!+sb-thread *free-tls-index*
171 #!+sb-thread *tls-index-lock*
173 *allocation-pointer*
174 *binding-stack-pointer*
176 ;; the floating point constants
177 *fp-constant-0d0*
178 *fp-constant-1d0*
179 *fp-constant-0f0*
180 *fp-constant-1f0*
182 ;; For GC-AND-SAVE
183 *restart-lisp-function*
185 ;; Needed for callbacks to work across saving cores. see
186 ;; ALIEN-CALLBACK-ASSEMBLER-WRAPPER in c-call.lisp for gory
187 ;; details.
188 sb!alien::*enter-alien-callback*
190 ;; The ..SLOT-UNBOUND.. symbol is static in order to optimise the
191 ;; common slot unbound check.
193 ;; FIXME: In SBCL, the CLOS code has become sufficiently tightly
194 ;; integrated into the system that it'd probably make sense to
195 ;; use the ordinary unbound marker for this.
197 ;; FIXME II: if it doesn't make sense, why is this X86-ish only?
198 sb!pcl::..slot-unbound..)))
200 (defparameter *static-funs*
201 '(length
202 sb!kernel:two-arg-+
203 sb!kernel:two-arg--
204 sb!kernel:two-arg-*
205 sb!kernel:two-arg-/
206 sb!kernel:two-arg-<
207 sb!kernel:two-arg->
208 sb!kernel:two-arg-=
210 sb!kernel:%negate
211 sb!kernel:two-arg-and
212 sb!kernel:two-arg-ior
213 sb!kernel:two-arg-xor
214 sb!kernel:two-arg-gcd
215 sb!kernel:two-arg-lcm))