Possibly mistaken usage of the cupyx.jit.thrust.device
execution policy in the JIT context?
#8239
Labels
cupyx.jit.thrust.device
execution policy in the JIT context?
#8239
When discussing the Thrust JIT support with the CCCL team, a question was raised regarding the usage of the
jit.thrust.device
policy in the test suite, ex:cupy/tests/cupyx_tests/jit_tests/test_thrust.py
Lines 954 to 959 in be5d7f6
jit.thrust.seq
instead. Before CUDA 12, using thedevice
policy would actually silently launch additional kernels using the "old" CUDA dynamic parallelism, so-called CDP1 in the CUDA Programming Guide (although why it worked without us passing-rdc
explicitly to the compiler remains to be seen). Worst of all, this is not something that a debugger or profiler can warn. Starting CUDA 12, it'd fall back to theseq
policy and at some point it will become a compile-time error.@jrhemstad @gevtushenko please correct me if the above summary is inaccurate 🙂 Thanks!
The text was updated successfully, but these errors were encountered: