Vincent Favre-Nicolin

I tested this also under windows 10 with CUDA 11.2 and the issue is reproduced with the above code snippet In the [CUDA 11.2 release notes](https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/) you can read among...

Under linux with cuda toolkit 11.5 installed in a conda environment (cufftGetVersion() reports 106000 ; driver 460.91.03), the issue is still present, even if the cuda release notes do not...

The reported error is not present anymore in numpy 1.19 (see https://github.com/numpy/numpy/issues/14384), so this can probably be closed. (Note that I did not reproduce this in scikit-cuda, but in another...

Is there any case where the `real` keyword is used beside realcomplex transforms ? Can I submit a PR deprecating this keyword ? Thanks, Vincent

I just saw the inline-real2real branch. No deprecation then ? But may be useful to recognize the complex hermitian->real transform without the keyword. Could inline real2real also be recognized automatically...

Nice to be able to see the complex data ! Some suggestions: - rename the type of display from 'Absolute' to 'Amplitude' - it may be better to initially display...

Having an environment variable like `PYCUDA_DEFAULT_JIT_ARCH` would be very useful. For custom kernels you can indeed use the `arch` argument, but this is not possible for ElementWise or Reduction kernels...

Hi @DTolm, - this is just to confirm that the issue seems fixed on HD graphics 5000 and UHD630 in my tests, but not on an Iris Graphics 6100. This...

Hi - I just hit that bug which is present since 0.19.0, as I was relying on the returned error to select the best configuration. I would support solution 1...

Yes it would be interesting if the Vulkan backend could be accessible as well. However I have no use for the Vulkan backend, so I can't work on this and...