topic thanks Roman, we will check in Intel® oneAPI Math Kernel Library

Typos in documentation

Marc_L_ — Fri, 04 Dec 2015 13:58:25 GMT

Hello,

I hope I am not polluting this forum with the following trivialities:

Is this the right place to report issues with MKL ?
There is a typo in the documentation of the page "v?LinearFrac" (in Section Vector Mathematical Functions).
The types of scalea, scaleb, shifta and shiftb are wrong, it should be "float" instead of "float *" (and "double" instead of "double *").
Finally, is it really pertinent to put a "const" in front on non-pointers values (eg. MKL_INT) ?

Source: https://software.intel.com/en-us/node/521774

Best regards,

Marc Lasson.

Hello Marc,

Gennady_F_Intel — Mon, 07 Dec 2015 06:21:00 GMT

Hello Marc,

yes this is the right place to report the issue with MKL.

You are right, the doc will be fixed.

Another typo, located in

Roman_F_ — Mon, 07 Dec 2015 17:20:01 GMT

Another typo, located in function mkl_?csrcoo, at input parameter job: if job[0]=2 (left square bracket is missing).

thanks Roman, we will check

Gennady_F_Intel — Tue, 08 Dec 2015 05:59:13 GMT

thanks Roman, we will check this too.

Another one:

Marc_L_ — Wed, 20 Jan 2016 16:07:54 GMT

Another one:

In the page about vslNewStreamEx https://software.intel.com/fr-fr/node/521854, the argument "params" should be of type "const unsigned int *" instead of "const unsigned int" (it is an array).

Cheers.

Hi Marc, good catch, thanks,

Andrey_N_Intel — Wed, 20 Jan 2016 16:14:34 GMT

Hi Marc, good catch, thanks, we will fix it in one of the next releases. Andrey

I put my remark here to avoid

Eugene_S_1 — Fri, 26 Feb 2016 10:56:26 GMT

I put my remark here to avoid adding a new topic. MKL Feast routines have the following declarations in (dfeast_scsrgv for example): _Mkl_Api(void,dfeast_scsrgv,(const char* uplo , const MKL_INT* n , const double* sa , const MKL_INT* isa , const MKL_INT* jsa , const double* sb , const MKL_INT* isb , const MKL_INT* jsb , MKL_INT* fpm , double* epsout , MKL_INT* loop , const double* emin , const double* emax , MKL_INT* m0 , double* e , double* x , MKL_INT* mode , double* res , MKL_INT* info)) I wonder why is it "mode" and not just "m" as the reference manual reads? Shouldn't the confusing "mode" be replaced with "m"?