Wrong result when using BLAS dot product routine (DDOT) from a MEX file

Question

José Goulart 2015-7-3

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/227890-wrong-result-when-using-blas-dot-product-routine-ddot-from-a-mex-file

评论： José Goulart 2015-7-5

Hello,

I am trying to call some BLAS routines from MEX code. First, I am trying to compute a scalar product with the fuction DDOT.

Here is my MEX file:

#include "mex.h"
#include "blas.h"
void mexFunction(int nlhs, mxArray *plhs[], int nrhs, const mxArray *prhs[])
{
  double *A, *B, C;
  int m, one=1;
  A = mxGetPr(prhs[0]);
  B = mxGetPr(prhs[1]);
  m = mxGetM(prhs[0]); /* number of rows */
    /* Pass all arguments to Fortran by reference */
    C = (double) ddot(&m,A,&one,B,&one);
    /* create output */
    plhs[0] = mxCreateDoubleScalar(C);
    return;
  }

The compilation returns no error. When using it, though, I do not get the expected result:

>> a = ones(2,1);
>> b = ones(2,1);
>> mydot(a,b)
ans =
       0

Am I calling DDOT inappropriately?

-- H. G.

1 个评论
显示 -1更早的评论隐藏 -1更早的评论

James Tursa 2015-7-4

I would advise using mxGetNumberOfElements instead of mxGetM, to make the routine a bit more robust for row vs column vector inputs.

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Titus Edelhofer 2015-7-3

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/227890-wrong-result-when-using-blas-dot-product-routine-ddot-from-a-mex-file#answer_184960

在 MATLAB Online 中打开

Hi,

you need to change the variable definition of m and one and use two variables for "one":

ptrdiff_t m, one1 = 1, one2 = 1;
C = (double) ddot(&m,A,&one1,B,&one2);

Then it works.

Titus

2 个评论
显示无隐藏无

James Tursa 2015-7-4

编辑：James Tursa 2015-7-4

mwSignedIndex is usually what is recommended for the integer arguments of BLAS and LAPACK functions for the libraries that MATLAB ships with ... at least that is what is used in the example code. I haven't scanned through the header files to see if this always reduces to ptrdiff_t or not.

Using two different variables for "one" should not be necessary ... all of the arguments are inputs that should be treated as read-only by DDOT.

José Goulart 2015-7-5