(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
#!+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