- ;; unbound_marker is borrowed very briefly at thread startup to
- ;; pass the address of initial-function into new_thread_trampoline
- (unbound-marker :init :unbound) ; tls[0] = UNBOUND_MARKER_WIDETAG
- (binding-stack-start :c-type "lispobj *")
- (binding-stack-pointer :c-type "lispobj *")
- (control-stack-start :c-type "lispobj *")
- (control-stack-end :c-type "lispobj *")
- (alien-stack-start :c-type "lispobj *")
- (alien-stack-pointer :c-type "lispobj *")
- (alloc-region :c-type "struct alloc_region" :length 5)
- (pid :c-type "pid_t")
- (tls-cookie) ; on x86, the LDT index
- (this :c-type "struct thread *")
- (next :c-type "struct thread *")
- (pseudo-atomic-atomic)
- (pseudo-atomic-interrupted)
- (interrupt-data :c-type "struct interrupt_data *")
+ ;; 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)
+ #!+sb-thread
+ (os-attr :c-type "pthread_attr_t *" :length #!+alpha 2 #!-alpha 1)
+ #!+sb-thread
+ (state-lock :c-type "pthread_mutex_t *" :length #!+alpha 2 #!-alpha 1)
+ #!+sb-thread
+ (state-cond :c-type "pthread_cond_t *" :length #!+alpha 2 #!-alpha 1)
+ (binding-stack-start :c-type "lispobj *" :length #!+alpha 2 #!-alpha 1)
+ (binding-stack-pointer :c-type "lispobj *" :length #!+alpha 2 #!-alpha 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)
+ #!+gencgc (alloc-region :c-type "struct alloc_region" :length 5)
+ (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
+ #!+(or x86 x86-64 sb-thread) (pseudo-atomic-bits)
+ (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.
+ #!+(and sb-thread)
+ (control-stack-pointer :c-type "lispobj *")
+ ;; 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)