[Octave-bug-tracker] [bug #64687] mxMalloc thread safety and mxCreateNumericArray performance

[anonymous]

Follow-up Comment #2, bug #64687 (project octave):

[comment #1 comment #1:]
> Another potential bug. The function mxGetElementSize() ignore complexity. It
returns 8 for double and also 8 for complex<double> whereas it should return
16. MATLAB returns 16.

Ah, I just realized this is a new(ish) change since 2018 when they switched to
interleaved complex numbers. The mex -R2018a flag solves it - apologies for
the noise!


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64687>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/