(define-primitive-object (bignum :lowtag other-pointer-lowtag
:widetag bignum-widetag
:alloc-trans sb!bignum::%allocate-bignum)
- (digits :rest-p t :c-type #!-alpha "long" #!+alpha "u32"))
+ (digits :rest-p t :c-type #!-alpha "sword_t" #!+alpha "u32"))
(define-primitive-object (ratio :type ratio
:lowtag other-pointer-lowtag
;; VECTOR -- see SHRINK-VECTOR.
(length :ref-trans sb!c::vector-length
:type index)
- (data :rest-p t :c-type #!-alpha "unsigned long" #!+alpha "u32"))
+ (data :rest-p t :c-type #!-alpha "uword_t" #!+alpha "u32"))
(define-primitive-object (code :type code-component
:lowtag other-pointer-lowtag
(define-primitive-object (binding)
value
- symbol)
+ symbol) ;; on sb-thread, this is actually a tls-index
(define-primitive-object (unwind-block)
(current-uwp :c-type #!-alpha "struct unwind_block *" #!+alpha "u32")
(current-cont :c-type #!-alpha "lispobj *" #!+alpha "u32")
#!-(or x86 x86-64) current-code
entry-pc
- #!+win32 next-seh-frame
- #!+win32 seh-frame-handler
+ #!+(and win32 x86) next-seh-frame
+ #!+(and win32 x86) seh-frame-handler
tag
(previous-catch :c-type #!-alpha "struct catch_block *" #!+alpha "u32"))
(package :ref-trans symbol-package
:set-trans %set-symbol-package
:init :null)
- #!+sb-thread (tls-index :ref-known (flushable) :ref-trans symbol-tls-index))
+ ;; 0 tls-index means no tls-index is allocated
+ #!+sb-thread
+ (tls-index :ref-known (flushable) :ref-trans symbol-tls-index))
(define-primitive-object (complex-single-float
:lowtag other-pointer-lowtag
(real :c-type "double" :length #!-x86-64 2 #!+x86-64 1)
(imag :c-type "double" :length #!-x86-64 2 #!+x86-64 1))
+#!+sb-simd-pack
+(define-primitive-object (simd-pack
+ :lowtag other-pointer-lowtag
+ :widetag simd-pack-widetag)
+ (tag :ref-trans %simd-pack-tag
+ :attributes (movable flushable)
+ :type fixnum)
+ (lo-value :c-type "long" :type (unsigned-byte 64))
+ (hi-value :c-type "long" :type (unsigned-byte 64)))
+
;;; 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
(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)
;; 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)
+ #!+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