Custom Query (1030 matches)

The macro new-pixel-format from the rubix opengl example code (in rubix/opengl.lisp) has been redefined as a function and does not appear to be functional. Error attached and here's the code which resulted in the error:

(opengl:new-pixel-format #$NSOpenGLPFAMultisample

#$NSOpenGLPFASampleAlpha #$NSOpenGLPFASampleBuffers 2 #$NSOpenGLPFASamples 4)

(it's a minor issue, but I do need the functionality as my non-example code uses it)

This code:

(defun matrix-times-matrix (mat1 mat2)
  "Multiplies two matrices together"
  (if (= (array-dimension mat1 1)
         (array-dimension mat2 0))
      (let ((result (make-array (list (array-dimension mat1 0)
                                      (array-dimension mat2 1)))))
        (dotimes (row (array-dimension result 0))
          (dotimes (column (array-dimension result 1))
            (let ((terms 0))
              (dotimes (middle (array-dimension mat1 1))
                (setf terms (+ terms (* (or (aref mat1 row middle) 0)
                                        (or (aref mat2 middle column) 0)))))
              (setf (aref result row column) terms))))
        (return-from matrix-times-matrix result))
      (progn
        (format t "~&Illegal matrix multiplication:
Matrix sizes ~a x ~a and ~a x ~a don't match."
                (array-dimension mat1 0)
                (array-dimension mat1 1)
                (array-dimension mat2 0)
                (array-dimension mat2 1))
        (return-from matrix-times-matrix nil))))

blows up in the compiler, when it discovers that it has to go through the write barrier at .SPgvset and that things are in the wrong registers for that.

It is possible that this just got exposed in 040708, because previous versions may have gotten MAKE-ARRAY type inferencing wrong

If a compare-and-swap (cmpxchgq) instruction used in the subprimitive _SPstore_node_conditional failed (cleard the z flag), the subsequent branch instruction branched forward to local label 0. It should have branched backward, retrying the store-conditional.

Branching backward typically caused code in _SPprogvsave - which checks to ensure that a list of values was a proper list - to signal a confusing, spurious error.