topic copy for integer array in Intel® oneAPI Math Kernel Library

copy for integer array

Ren_J_ — Wed, 23 Mar 2016 11:46:38 GMT

Hello,

I have a naive question about that why there is only float array copy .

Is the time cost of integer array copy much smaller than float number copy?

Best Regards,

Jiajun

If we are just copying (no

Murat_G_Intel — Wed, 23 Mar 2016 19:55:02 GMT

If we are just copying (no scaling), there is no difference between integer vs. float. We copy bits from one memory location to another and it does not mater what those bits represent (integer/float/string/etc..). memcpy can be used for this operation. If you really want to use MKL, you can typecast your 32bit integer pointers to float* and call scopy. Similarly, you can typecast your 64bit integer pointers to doubles* and call dcopy.

Intel Fortran and C++

TimP — Wed, 23 Mar 2016 21:21:35 GMT

Intel Fortran and C++ compilers would likely substitute intel_fast_memcpy when optimizing a single isolated loop. MKL ?copy have a potential higher bandwidth when parallelizing internally across multiple CPUs, if the source and destination have suitable NUMA locality.

Either an optimized memcpy or MKL ?copy should look for the case where non-temporal streaming store is preferred.

The short answer is that compilers can usually make as good or better choice when the programmer leaves the details to the compilers.

Quote:Murat Efe Guney (Intel)

Ren_J_ — Mon, 28 Mar 2016 13:09:22 GMT

Murat Efe Guney (Intel) wrote:

If we are just copying (no scaling), there is no difference between integer vs. float. We copy bits from one memory location to another and it does not mater what those bits represent (integer/float/string/etc..). memcpy can be used for this operation. If you really want to use MKL, you can typecast your 32bit integer pointers to float* and call scopy. Similarly, you can typecast your 64bit integer pointers to doubles* and call dcopy.

I use fortran. It seems that Fortran 95 interface do not support integer copy.

for example

==============

integer a(10),b(10)

call copy(a,b)

==============

It doesn't work.

But f77 interface works.

==============

call scopy(10,a,1,b,1)

==============

Yes, you would have to add

TimP — Mon, 28 Mar 2016 13:55:59 GMT

Yes, you would have to add the corresponding interface block to blas.f90 (and disable warn_interfaces) to persuade the compiler to use the scopy or dcopy for integer types.