Add a "known issues & limitations" page
Open
Nobody has claimed this yet.
cuda.core
documentation
- Dominant language
- Cython
- Stars
- 3.4k
- Forks
- 329
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 116
Description
- cuda.core does not allow any side calls to
cudaDeviceResetor alike that tear down the primary contexts - avoid multiple frees of the same buffer in the child process (https://github.com/NVIDIA/cuda-python/issues/1074#issuecomment-3367798948, #1118)
- when going out of scope without an explicit
.close()call, a buffer is deallocated on the allocation stream (https://github.com/NVIDIA/cuda-python/pull/1032) - compute-sanitizer needs a flag to work with cuda.core (https://github.com/NVIDIA/cuda-python/issues/562#issuecomment-3009049723)
- ...
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 documentation file or entry point is named. Review the listed CUDA Python issues and pull request, then locate the repository's existing documentation structure; done means a known-issues and limitations page covers the listed cases with accurate references and context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100