+ (real :c-type "double" :length #!-x86-64 2 #!+x86-64 1)
+ (imag :c-type "double" :length #!-x86-64 2 #!+x86-64 1))
+
+;;; this isn't actually a lisp object at all, it's a c structure that lives
+;;; in c-land. However, we need sight of so many parts of it from Lisp that
+;;; it makes sense to define it here anyway, so that the GENESIS machinery
+;;; can take care of maintaining Lisp and C versions.
+(define-primitive-object (thread)
+ ;; no_tls_value_marker is borrowed very briefly at thread startup to
+ ;; pass the address of initial-function into new_thread_trampoline.
+ ;; tls[0] = NO_TLS_VALUE_MARKER_WIDETAG because a the tls index slot
+ ;; of a symbol is initialized to zero
+ (no-tls-value-marker)
+ (os-thread :c-type "os_thread_t")
+ ;; This is the original address at which the memory was allocated,
+ ;; which may have different alignment then what we prefer to use.
+ ;; Kept here so that when the thread dies we can release the whole
+ ;; memory we reserved.
+ (os-address :c-type "void *" :length #!+alpha 2 #!-alpha 1)
+ ;; Keep these next four slots close to the beginning of the structure.
+ ;; Doing so reduces code size for x86-64 allocation sequences and
+ ;; special variable manipulations.
+ #!+gencgc (alloc-region :c-type "struct alloc_region" :length 5)
+ #!+(or x86 x86-64 sb-thread) (pseudo-atomic-bits)
+ (binding-stack-start :c-type "lispobj *" :length #!+alpha 2 #!-alpha 1)
+ (binding-stack-pointer :c-type "lispobj *" :length #!+alpha 2 #!-alpha 1)
+ #!+sb-thread
+ (os-attr :c-type "pthread_attr_t *" :length #!+alpha 2 #!-alpha 1)
+ #!+sb-thread
+ (state-sem :c-type "os_sem_t *" :length #!+alpha 2 #!-alpha 1)
+ #!+sb-thread
+ (state-not-running-sem :c-type "os_sem_t *" :length #!+alpha 2 #!-alpha 1)
+ #!+sb-thread
+ (state-not-running-waitcount :c-type "int" :length 1)
+ #!+sb-thread
+ (state-not-stopped-sem :c-type "os_sem_t *" :length #!+alpha 2 #!-alpha 1)
+ #!+sb-thread
+ (state-not-stopped-waitcount :c-type "int" :length 1)
+ (control-stack-start :c-type "lispobj *" :length #!+alpha 2 #!-alpha 1)
+ (control-stack-end :c-type "lispobj *" :length #!+alpha 2 #!-alpha 1)
+ (control-stack-guard-page-protected)
+ (alien-stack-start :c-type "lispobj *" :length #!+alpha 2 #!-alpha 1)
+ (alien-stack-pointer :c-type "lispobj *" :length #!+alpha 2 #!-alpha 1)
+ #!+win32 (private-events :c-type "struct private_events" :length 2)
+ (this :c-type "struct thread *" :length #!+alpha 2 #!-alpha 1)
+ (prev :c-type "struct thread *" :length #!+alpha 2 #!-alpha 1)
+ (next :c-type "struct thread *" :length #!+alpha 2 #!-alpha 1)
+ ;; starting, running, suspended, dead
+ (state :c-type "lispobj")
+ (tls-cookie) ; on x86, the LDT index
+ (interrupt-data :c-type "struct interrupt_data *"
+ :length #!+alpha 2 #!-alpha 1)
+ (stepping)
+ ;; For various reasons related to pseudo-atomic and interrupt
+ ;; handling, we need to know if the machine context is in Lisp code
+ ;; or not. On non-threaded targets, this is a global variable in
+ ;; the runtime, but it's clearly a per-thread value.
+ #!+sb-thread
+ (foreign-function-call-active :c-type "boolean")
+ ;; Same as above for the location of the current control stack frame.
+ #!+(and sb-thread (not (or x86 x86-64)))
+ (control-frame-pointer :c-type "lispobj *")
+ ;; Same as above for the location of the current control stack
+ ;; pointer. This is also used on threaded x86oids to allow LDB to
+ ;; print an approximation of the CSP as needed.
+ #!+sb-thread
+ (control-stack-pointer :c-type "lispobj *")
+ #!+mach-exception-handler
+ (mach-port-name :c-type "mach_port_name_t")
+ (nonpointer-data :c-type "struct nonpointer_thread_data *" :length #!+alpha 2 #!-alpha 1)
+ #!+(and sb-safepoint x86) (selfptr :c-type "struct thread *")
+ ;; Context base pointer for running on top of system libraries built using
+ ;; -fomit-frame-pointer. Currently truly required and implemented only
+ ;; for (and win32 x86-64), but could be generalized to other platforms if
+ ;; needed:
+ #!+win32 (carried-base-pointer :c-type "os_context_register_t")
+ #!+sb-safepoint (csp-around-foreign-call :c-type "lispobj *")
+ #!+sb-safepoint (pc-around-foreign-call :c-type "lispobj *")
+ #!+win32 (synchronous-io-handle-and-flag :c-type "HANDLE" :length 1)
+ #!+(and sb-safepoint-strictly (not win32))
+ (sprof-alloc-region :c-type "struct alloc_region" :length 5)
+ ;; KLUDGE: On alpha, until STEPPING we have been lucky and the 32
+ ;; bit slots came in pairs. However the C compiler will align
+ ;; interrupt_contexts on a double word boundary. This logic should
+ ;; be handled by DEFINE-PRIMITIVE-OBJECT.
+ #!+alpha
+ (padding)
+ (interrupt-contexts :c-type "os_context_t *" :rest-p t))