Serialization and deserialization of kernel
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 456
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
Required prerequisites
- Search the issue tracker to check if your feature has already been mentioned or rejected in other issues.
Describe the feature
The ability to save and load the kernel is needed.
The use case is, for example, to save kernels, used as a cache, or broadcast with MPI.
There are many ways to implement this: QASM3, some MLIR, or even the original format.
Requirements
- not only Python but also C++
- Backward compatibility, i.e., you can load a saved kernel from a future version
Reference: CUDA has JIT feature and it can be stored.
Deserialization is related to https://github.com/NVIDIA/cuda-quantum/issues/755
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reviewing issue 755 and the linked CUDA NVRTC and Jitify references, then identify the existing kernel representations and APIs for both C++ and Python. Done means an agreed serialization approach supports saving and loading in both languages with the requested backward-compatibility guarantees.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100