[Matlisp-users] thread safety

[Evan M. <eva...@gm...>]

Hi,

I have been using matlisp for a little while now, and I started to look
inside matlisp files to see if it was thread-safe.

One issue that I have found is that functions like
DGEEV-WORKSPACE-INQUIRY are closures around matrices of size one which
are used to store the size of the work matrix.

If I call DGEEV-WORKSPACE-INQUIRY simultaneously in several threads, it
might happen that the values that are read/written in this matrix will
be polluted by the other threads.

other examples are:

DGEEV-workspace-inquiry
zgeev-workspace-inquiry
GEMM!
dgeqrf-workspace-inquiry
zgeqrf-workspace-inquiry
dgeqp3-workspace-inquiry
zgeqp3-workspace-inquiry

I may have missed others, as I looked only at toplevel LET bindings.

Evan