[FEA] JIT Compilation of CUDF Kernels

[lamarrr]

Is your feature request related to a problem? Please describe. As described in #15366, we intend to adopt JIT compilation to some of our kernels using JITify/NVRTC. JITify presently only supports compilation of device code, this means we can't mix host code with it, like we'd do with NVCC. Some important headers are not supported, i.e.

• <stdexcept>
• <atomic> (replace with cuda/std/atomic)

Describe the solution you'd like We'd need to:

• Separate headers required in kernel code into device-only and host-only code headers
• Patch Thrust and RMM headers to separate their headers into device-only code headers

Describe alternatives you've considered

• Using macros to separate the device-only code from host code, this doesn't work and would have been very brittle
• Depending on NVCC for PTX and loading it into the driver at runtime

[jrhemstad]

Patch Thrust and RMM headers to separate their headers into device-only code headers

Please no. RAPIDS is banned from applying any more patches to Thrust headers 🙂

You should only include RMM or Thrust headers in the host-only headers, so there shouldn't be any need to modify those.