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

[John W. Eaton]

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

In the example in comment #3, did you use the option to create an array of
interleaved complex values?  If not, then I think you are seeing the expected
result as mxGetData will return a pointer to the array of real values and that
will just contain 9 double values.

BTW, Matlab docs appear to discourage using mxGetData for numeric arrays and
warn that the meaning of the pointer it returns depends on whether the mex
file has been compiled to use interleaved complex values or not.

If you still think there is a bug here, then please upload a complete mex file
that shows the bug and show us exactly what command you use to compile the mex
function.

Also, backticks and other markdown formatting commands don't work in the bug
tracker.  To avoid confusion, please use the +/-verbatim+/- tags for code
snippets.  Without those, code parts probably won't be formatted correctly.

Finally, please open separate bug reports for separate issues.  Inserting new
problems in an existing report also leads to confusion.


    _______________________________________________________

Reply to this item at:

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

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