1 ;;;; X86-specific runtime stuff
3 ;;;; This software is part of the SBCL system. See the README file for
6 ;;;; This software is derived from the CMU CL system, which was
7 ;;;; written at Carnegie Mellon University and released into the
8 ;;;; public domain. The software is in the public domain and is
9 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
10 ;;;; files for more information.
16 ;;; a POSIX signal context, i.e. the type passed as the third
17 ;;; argument to an SA_SIGACTION-style signal handler
19 ;;; The real type does have slots, but at Lisp level, we never
20 ;;; access them, or care about the size of the object. Instead, we
21 ;;; always refer to these objects by pointers handed to us by the C
22 ;;; runtime library, and ask the runtime library any time we need
23 ;;; information about the contents of one of these objects. Thus, it
24 ;;; works to represent this as an object with no slots.
26 ;;; KLUDGE: It would be nice to have a type definition analogous to
27 ;;; C's "struct os_context_t;", for an incompletely specified object
28 ;;; which can only be referred to by reference, but I don't know how
29 ;;; to do that in the FFI, so instead we just this bogus no-slots
30 ;;; representation. -- WHN 20000730
32 ;;; FIXME: Since SBCL, unlike CMU CL, uses this as an opaque type,
33 ;;; it's no longer architecture-dependent, and probably belongs in
34 ;;; some other package, perhaps SB-KERNEL.
35 (define-alien-type os-context-t (struct os-context-t-struct))
37 ;;;; MACHINE-TYPE and MACHINE-VERSION
39 (defun machine-type ()
41 "Return a string describing the type of the local machine."
44 ;;; arch-specific support for CL:MACHINE-VERSION, defined OAOO elsewhere
45 (defun get-machine-version ()
47 (with-open-file (stream "/proc/cpuinfo"
48 ;; Even on Linux it's an option to build
49 ;; kernels without /proc filesystems, so
50 ;; degrade gracefully.
51 :if-does-not-exist nil)
52 (loop with line while (setf line (read-line stream nil))
53 ;; The field "model name" exists on kernel 2.4.21-rc6-ac1
54 ;; anyway, with values e.g.
55 ;; "AMD Athlon(TM) XP 2000+"
56 ;; "Intel(R) Pentium(R) M processor 1300MHz"
57 ;; which seem comparable to the information in the example
58 ;; in the MACHINE-VERSION page of the ANSI spec.
59 when (eql (search "model name" line) 0)
60 return (string-trim " " (subseq line (1+ (position #\: line))))))
64 ;;;; :CODE-OBJECT fixups
66 ;;; a counter to measure the storage overhead of these fixups
67 (defvar *num-fixups* 0)
68 ;;; FIXME: When the system runs, it'd be interesting to see what this is.
70 (declaim (inline adjust-fixup-array))
71 (defun adjust-fixup-array (array size)
72 (let ((new (make-array size :element-type '(unsigned-byte 32))))
76 ;;; This gets called by LOAD to resolve newly positioned objects
77 ;;; with things (like code instructions) that have to refer to them.
79 ;;; Add a fixup offset to the vector of fixup offsets for the given
81 (defun fixup-code-object (code offset fixup kind)
82 (declare (type index offset))
83 (flet ((add-fixup (code offset)
84 ;; (We check for and ignore fixups for code objects in the
85 ;; read-only and static spaces. (In the old CMU CL code
86 ;; this check was conditional on *ENABLE-DYNAMIC-SPACE-CODE*,
87 ;; but in SBCL relocatable dynamic space code is always in
88 ;; use, so we always do the check.)
90 (let ((fixups (code-header-ref code code-constants-offset)))
91 (cond ((typep fixups '(simple-array (unsigned-byte 32) (*)))
93 (adjust-fixup-array fixups (1+ (length fixups)))))
94 (setf (aref new-fixups (length fixups)) offset)
95 (setf (code-header-ref code code-constants-offset)
98 (unless (or (eq (widetag-of fixups)
99 unbound-marker-widetag)
101 (format t "** Init. code FU = ~S~%" fixups)) ; FIXME
102 (setf (code-header-ref code code-constants-offset)
105 :element-type '(unsigned-byte 32)
106 :initial-element offset)))))))
107 (sb!sys:without-gcing
108 (let* ((sap (truly-the system-area-pointer
109 (sb!kernel:code-instructions code)))
110 (obj-start-addr (logand (sb!kernel:get-lisp-obj-address code)
112 ;; FIXME: what is this 5?
113 #+nil (const-start-addr (+ obj-start-addr (* 5 n-word-bytes)))
114 (code-start-addr (sb!sys:sap-int (sb!kernel:code-instructions
116 (ncode-words (sb!kernel:code-header-ref code 1))
117 (code-end-addr (+ code-start-addr (* ncode-words n-word-bytes))))
118 (unless (member kind '(:absolute :relative))
119 (error "Unknown code-object-fixup kind ~S." kind))
122 ;; Word at sap + offset contains a value to be replaced by
123 ;; adding that value to fixup.
124 (setf (sap-ref-32 sap offset) (+ fixup (sap-ref-32 sap offset)))
125 ;; Record absolute fixups that point within the code object.
126 (when (> code-end-addr (sap-ref-32 sap offset) obj-start-addr)
127 (add-fixup code offset)))
129 ;; Fixup is the actual address wanted.
131 ;; Record relative fixups that point outside the code
133 (when (or (< fixup obj-start-addr) (> fixup code-end-addr))
134 (add-fixup code offset))
135 ;; Replace word with value to add to that loc to get there.
136 (let* ((loc-sap (+ (sap-int sap) offset))
137 (rel-val (- fixup loc-sap n-word-bytes)))
138 (declare (type (unsigned-byte 32) loc-sap)
139 (type (signed-byte 32) rel-val))
140 (setf (signed-sap-ref-32 sap offset) rel-val))))))
143 ;;; Add a code fixup to a code object generated by GENESIS. The fixup
144 ;;; has already been applied, it's just a matter of placing the fixup
145 ;;; in the code's fixup vector if necessary.
147 ;;; KLUDGE: I'd like a good explanation of why this has to be done at
148 ;;; load time instead of in GENESIS. It's probably simple, I just haven't
149 ;;; figured it out, or found it written down anywhere. -- WHN 19990908
151 (defun !envector-load-time-code-fixup (code offset fixup kind)
152 (flet ((frob (code offset)
153 (let ((fixups (code-header-ref code code-constants-offset)))
154 (cond ((typep fixups '(simple-array (unsigned-byte 32) (*)))
156 (adjust-fixup-array fixups (1+ (length fixups)))))
157 (setf (aref new-fixups (length fixups)) offset)
158 (setf (code-header-ref code code-constants-offset)
161 (unless (or (eq (widetag-of fixups)
162 unbound-marker-widetag)
164 (sb!impl::!cold-lose "Argh! can't process fixup"))
165 (setf (code-header-ref code code-constants-offset)
168 :element-type '(unsigned-byte 32)
169 :initial-element offset)))))))
170 (let* ((sap (truly-the system-area-pointer
171 (sb!kernel:code-instructions code)))
173 ;; FIXME: looks like (LOGANDC2 foo typebits)
174 (logand (sb!kernel:get-lisp-obj-address code) #xfffffff8))
175 (code-start-addr (sb!sys:sap-int (sb!kernel:code-instructions
177 (ncode-words (sb!kernel:code-header-ref code 1))
178 (code-end-addr (+ code-start-addr (* ncode-words n-word-bytes))))
181 ;; Record absolute fixups that point within the code object.
182 (when (> code-end-addr (sap-ref-32 sap offset) obj-start-addr)
185 ;; Record relative fixups that point outside the code object.
186 (when (or (< fixup obj-start-addr) (> fixup code-end-addr))
187 (frob code offset)))))))
189 ;;;; low-level signal context access functions
191 ;;;; Note: In CMU CL, similar functions were hardwired to access
192 ;;;; BSD-style sigcontext structures defined as alien objects. Our
193 ;;;; approach is different in two ways:
194 ;;;; 1. We use POSIX SA_SIGACTION-style signals, so our context is
195 ;;;; whatever the void pointer in the sigaction handler dereferences
196 ;;;; to, not necessarily a sigcontext.
197 ;;;; 2. We don't try to maintain alien definitions of the context
198 ;;;; structure at Lisp level, but instead call alien C functions
199 ;;;; which take care of access for us. (Since the C functions can
200 ;;;; be defined in terms of system standard header files, they
201 ;;;; should be easier to maintain; and since Lisp code uses signal
202 ;;;; contexts only in interactive or exception code (like the debugger
203 ;;;; and internal error handling) the extra runtime cost should be
206 (define-alien-routine ("os_context_pc_addr" context-pc-addr) (* unsigned-int)
207 ;; (Note: Just as in CONTEXT-REGISTER-ADDR, we intentionally use an
208 ;; 'unsigned *' interpretation for the 32-bit word passed to us by
209 ;; the C code, even though the C code may think it's an 'int *'.)
210 (context (* os-context-t)))
212 (defun context-pc (context)
213 (declare (type (alien (* os-context-t)) context))
214 (let ((addr (context-pc-addr context)))
215 (declare (type (alien (* unsigned-int)) addr))
216 (int-sap (deref addr))))
218 (define-alien-routine ("os_context_register_addr" context-register-addr)
220 ;; (Note the mismatch here between the 'int *' value that the C code
221 ;; may think it's giving us and the 'unsigned *' value that we
222 ;; receive. It's intentional: the C header files may think of
223 ;; register values as signed, but the CMU CL code tends to think of
224 ;; register values as unsigned, and might get bewildered if we ask
225 ;; it to work with signed values.)
226 (context (* os-context-t))
229 (defun context-register (context index)
230 (declare (type (alien (* os-context-t)) context))
231 (let ((addr (context-register-addr context index)))
232 (declare (type (alien (* unsigned-int)) addr))
235 (defun %set-context-register (context index new)
236 (declare (type (alien (* os-context-t)) context))
237 (let ((addr (context-register-addr context index)))
238 (declare (type (alien (* unsigned-int)) addr))
239 (setf (deref addr) new)))
241 ;;; This is like CONTEXT-REGISTER, but returns the value of a float
242 ;;; register. FORMAT is the type of float to return.
244 ;;; As of sbcl-0.6.7, there is no working code which calls this code,
245 ;;; so it's stubbed out. Someday, in order to make the debugger work
246 ;;; better, it may be necessary to unstubify it.
247 (defun context-float-register (context index format)
248 (declare (ignore context index))
249 (warn "stub CONTEXT-FLOAT-REGISTER")
251 (defun %set-context-float-register (context index format new-value)
252 (declare (ignore context index))
253 (warn "stub %SET-CONTEXT-FLOAT-REGISTER")
254 (coerce new-value format))
256 ;;; Given a signal context, return the floating point modes word in
257 ;;; the same format as returned by FLOATING-POINT-MODES.
259 (defun context-floating-point-modes (context)
260 ;; FIXME: As of sbcl-0.6.7 and the big rewrite of signal handling for
261 ;; POSIXness and (at the Lisp level) opaque signal contexts,
262 ;; this is stubified. It needs to be rewritten as an
264 (declare (ignore context)) ; stub!
265 (warn "stub CONTEXT-FLOATING-POINT-MODES")
267 ;; old code for Linux:
269 (let ((cw (slot (deref (slot context 'fpstate) 0) 'cw))
270 (sw (slot (deref (slot context 'fpstate) 0) 'sw)))
271 ;;(format t "cw = ~4X~%sw = ~4X~%" cw sw)
272 ;; NOT TESTED -- Clear sticky bits to clear interrupt condition.
273 (setf (slot (deref (slot context 'fpstate) 0) 'sw) (logandc2 sw #x3f))
274 ;;(format t "new sw = ~X~%" (slot (deref (slot context 'fpstate) 0) 'sw))
275 ;; Simulate floating-point-modes VOP.
276 (logior (ash (logand sw #xffff) 16) (logxor (logand cw #xffff) #x3f)))
281 (define-alien-routine ("os_context_fp_control" context-floating-point-modes)
282 (sb!alien:unsigned 32)
283 (context (* os-context-t)))
285 ;;;; INTERNAL-ERROR-ARGS
287 ;;; Given a (POSIX) signal context, extract the internal error
288 ;;; arguments from the instruction stream.
289 (defun internal-error-args (context)
290 (declare (type (alien (* os-context-t)) context))
291 (/show0 "entering INTERNAL-ERROR-ARGS, CONTEXT=..")
293 (let ((pc (context-pc context)))
294 (declare (type system-area-pointer pc))
296 ;; using INT3 the pc is .. INT3 <here> code length bytes...
297 (let* ((length (sap-ref-8 pc 1))
298 (vector (make-array length :element-type '(unsigned-byte 8))))
299 (declare (type (unsigned-byte 8) length)
300 (type (simple-array (unsigned-byte 8) (*)) vector))
301 (/show0 "LENGTH,VECTOR,ERROR-NUMBER=..")
304 (copy-from-system-area pc (* n-byte-bits 2)
305 vector (* n-word-bits vector-data-offset)
306 (* length n-byte-bits))
308 (error-number (sb!c:read-var-integer vector index)))
309 (/hexstr error-number)
310 (collect ((sc-offsets))
314 (when (>= index length)
316 (let ((sc-offset (sb!c:read-var-integer vector index)))
317 (/show0 "SC-OFFSET=..")
319 (sc-offsets sc-offset)))
320 (values error-number (sc-offsets)))))))
322 ;;; This is used in error.lisp to insure that floating-point exceptions
323 ;;; are properly trapped. The compiler translates this to a VOP.
329 ;;; These are used by the FP MOVE-FROM-{SINGLE|DOUBLE} VOPs rather
330 ;;; than the i387 load constant instructions to avoid consing in some
331 ;;; cases. Note these are initialized by GENESIS as they are needed
333 (defvar *fp-constant-0f0*)
334 (defvar *fp-constant-1f0*)
335 (defvar *fp-constant-0d0*)
336 (defvar *fp-constant-1d0*)
337 ;;; the long-float constants
338 (defvar *fp-constant-0l0*)
339 (defvar *fp-constant-1l0*)
340 (defvar *fp-constant-pi*)
341 (defvar *fp-constant-l2t*)
342 (defvar *fp-constant-l2e*)
343 (defvar *fp-constant-lg2*)
344 (defvar *fp-constant-ln2*)
346 ;;; the current alien stack pointer; saved/restored for non-local exits
347 (defvar *alien-stack*)
349 ;;; Support for the MT19937 random number generator. The update
350 ;;; function is implemented as an assembly routine. This definition is
351 ;;; transformed to a call to the assembly routine allowing its use in
352 ;;; interpreted code.
353 (defun random-mt19937 (state)
354 (declare (type (simple-array (unsigned-byte 32) (627)) state))
355 (random-mt19937 state))