Compile runtime text code about luisacompute HOT 6 CLOSED

Oh, I see :-)

This feature is not exposed, but should be easy to implement as it is what the backends actually do (example: the CUDACompiler::compile() method). I would like to help refactor this into a standalone method if you need it.

The tricky part would be making the source compatible with other parts of the DSL and runtime. For example, we would need certain mechanism to "reflect" the arguments and resource usages from the source string, so that the argument binding and command scheduling functionalities could work.

Another (possibly) useful approach is to support injections of "custom" operations into the DSL as part of a kernel, by using a similar syntax to inline assembly. We think this might be a valid solution to easily extending the system and are planning the feature in the next version of LuisaCompute.

from luisacompute.

Yes.

LuisaCompute traces and records (unified) kernel ASTs at runtime, and generates the shader sources and compiles them into PSO/CUDA modules with different backends. This design should well fit the use cases of node-based systems with dynamically assembled and compiled kernels/shaders.

For the CUDA backend (in which I assume you are interested), code generation is implemented in src/backends/cuda/cuda_codegen.[cpp|h], and compilation in src/backends/cuda/cuda_compiler.[cpp|h] (which uses NVRTC as well).

For more information (e.g., motivations, design principles, technical details), you might be interested in the original paper. We also have a proof-of-concept renderer that also implements a dynamic node-based system.

from luisacompute.

Hi thanks for the information. I first read your SIGGRAPH paper, and then I am here!
I understand LuisaCompute performs JIT compile at runtime, however what we are concerned about is whether it's possible to compile a kernel from a string (assume the content is source code written in LuisaCompute's DSL), which is procedurally generated. As far as I am aware, currently the Device::compile function only takes kernel objects. I guess there should be a way to generate kernel from string but don't know where it is. Of course LuisaCompute is fully capable for it, just wonder if this feature is already implemented.

from luisacompute.

Hi yes seems both approaches would work. Previously we did pretty much similar with your second approach. Either way, we will first try a bit further with LuisaCompute and see what we really want. Maybe we can contribute a bit to this project too.

from luisacompute.

Thanks! And looking forward to your good news!

from luisacompute.

We have (experimentally) introduced a simple "native include" feature recently, which allows users to include code segments written in the native shading language and call the imported ExternalCallables. Example is here: test_native_include.

The method still has some limitations, e.g., resources are not supported and no type checks are performed. We will try to improve it in the future.

from luisacompute.