:ref-known (flushable foldable)
:set-trans (setf %array-displaced-p)
:set-known (unsafe))
+ (displaced-from :type list
+ :ref-trans %array-displaced-from
+ :ref-known (flushable)
+ :set-trans (setf %array-displaced-from)
+ :set-known (unsafe)
+ :cas-trans %compare-and-swap-array-displaced-from
+ :cas-known (unsafe))
(dimensions :rest-p t))
(define-primitive-object (vector :type vector
(define-primitive-object (value-cell :lowtag other-pointer-lowtag
:widetag value-cell-header-widetag
+ ;; FIXME: We also have an explicit VOP
+ ;; for this. Is this needed as well?
:alloc-trans make-value-cell)
(value :set-trans value-cell-set
:set-known (unsafe)
#!+win32 next-seh-frame
#!+win32 seh-frame-handler
tag
- (previous-catch :c-type #!-alpha "struct catch_block *" #!+alpha "u32")
- size)
+ (previous-catch :c-type #!-alpha "struct catch_block *" #!+alpha "u32"))
;;; (For an explanation of this, see the comments at the definition of
;;; KLUDGE-NONDETERMINISTIC-CATCH-BLOCK-SIZE.)
(plist :ref-trans symbol-plist
:set-trans %set-symbol-plist
:cas-trans %compare-and-swap-symbol-plist
+ :type list
:init :null)
(name :ref-trans symbol-name :init :arg)
(package :ref-trans symbol-package
;; 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 "volatile os_thread_t")
+ (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)
(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 "volatile lispobj")
+ (state :c-type "lispobj")
(tls-cookie) ; on x86, the LDT index
#!+(or x86 x86-64) (pseudo-atomic-bits)
(interrupt-data :c-type "struct interrupt_data *"
:length #!+alpha 2 #!-alpha 1)
(stepping)
+ ;; 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))