GPU/CUDA API Change with Interleaved Complex Data

Were there changes to the CUDA C-API with 2018a and the new layout of interleaved complex data? Are there differences in syntax between compiling with -R2018a and -R2017b, or does it make a difference?

I see that mxGetData/mxGetImagData is no longer recommended with the 2017b (and prior) C-API, but mxGPUGetData is still shown as the default way to get data on the GPU even in later releases. How does this relate to handling complex data? Does it return mxComplexSingle(/Double/etc) format?

[James Tursa]

According to the online doc mxGPUGetData returns a (void *) type and it is up to you to cast it properly for downstream use.

Answer 1

[Edric Ellis]

gpuArray data has always been stored in complex-interleaved format since its introduction in R2010b. The mxGPUGetData function always returns a pointer to the interleaved data.