Custom Query (1030 matches)

document get-fpu-mode and set-fpu-mode

Running "Version 1.3-dev-r11488M-trunk (LinuxX8632)",

(coerce #(127 0 0 256) '(simple-array (unsigned-byte 8) (*)))

signals a SIMPLE-ERROR instead of a TYPE-ERROR.

Error:

256 doesn't match array element type of #(127 0 0 0).
   [Condition of type SIMPLE-ERROR]

Backtrace:
  0: (CCL::INIT-UVECTOR-CONTENTS #(127 0 0 0) 3 4 #(127 0 0 256))
      Locals:
        CCL::VECT = #(127 0 0 0)
        CCL::OFFSET = 3
        CCL::DIMS = 4
        CCL::CONTENTS = #(127 0 0 256)
        CCL::LEN = 4
        CCL::I = 3
  1: (CCL::MAKE-UARRAY-1 207 4 NIL NIL NIL NIL #(127 0 0 256) T NIL 4)
      Locals:
        CCL::SUBTYPE = 207
        CCL::DIMS = 4
        CCL::ADJUSTABLE = NIL
        FILL-POINTER = NIL
        CCL::INITIAL-ELEMENT = NIL
        CCL::INITIAL-ELEMENT-P = NIL
        CCL::INITIAL-CONTENTS = #(127 0 0 256)
        CCL::INITIAL-CONTENTS-P = T
        CCL::TEMPORARY = NIL
        CCL::SIZE = 4
        VECTOR = #(127 0 0 0)
  2: (CCL::CALL-CHECK-REGS COERCE #(127 0 0 256) (SIMPLE-ARRAY (UNSIGNED-BYTE 8) (*)))
      Locals:
        CCL::FN = COERCE
        CCL::ARGS = (#(127 0 0 256) (SIMPLE-ARRAY (UNSIGNED-BYTE 8) (*)))
        CCL::OLD-REGS = NIL

Typing c-/ at the lisp process (in a unix shell) leaves it in a weird state where ps lists it as <defunct>, but it actually keeps running, sometimes apparently working fine, sometimes becoming non-responsive.

Gary knows what causes this, but it might be hard to fix on some platforms.