Closed
Description
Heard some people complaining about the one-time only cost
https://docs.cupy.dev/en/stable/upgrade.html#modernized-cccl-support-and-requirement
which appears as if it hangs.
As a stop-gap solution, we should print a warning "jitify cache building, it may take a while..."
Short-term, I am thinking to extend @kmaehashi's idea that we implemented
generate a hash string of all
cupy/_core/include/**files at the build time and set it as a key
and build the json-based Jitify cache at build time, and ship it as part of the wheel and conda package.
Long term, I am afraid Jitify's default compile-fail-search loop is too expansive and we might have to either implement it ourselves or use the WIP (NVIDIA/jitify#131).