deepseek-ai/DeepGEMM
1
0
Fork 0
mirror of https://github.com/deepseek-ai/DeepGEMM.git synced 2026-11-05 00:47:26 +00:00
Code Issues 162 Projects Packages Wiki Activity

[GH-ISSUE #358] [Feature request] Documented clangd setup for CUDA kernel indexing #169

New issue
Open
opened 2026-10-26 21:14:06 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-26 21:14:06 +00:00
Owner
Copy link

Originally created by @Rachmanino on GitHub (Jun 12, 2026).
Original GitHub issue: https://github.com/deepseek-ai/DeepGEMM/issues/358

DeepGEMM already has a CMake path intended for IDE indexing, but clangd setup is currently not straightforward for CUDA headers.

In my local setup I needed:

  • a dedicated build-clangd directory with CMAKE_EXPORT_COMPILE_COMMANDS=ON
  • pybind11/Torch CMake prefixes passed explicitly
  • .clangd CUDA flags for .cuh files, e.g. -x cuda, --cuda-gpu-arch=sm_100, --cuda-path=...
  • removal of some nvcc-only flags
  • a few diagnostic suppressions for CUDA 13.x / SM100 false positives

Would the project be open to adding either:

  1. a short clangd setup section in the README, or
  2. a helper script such as scripts/configure_clangd.sh, or
  3. a checked-in template .clangd.example?

The goal would be reliable navigation/indexing for kernel development, not necessarily zero clang diagnostics for all CUDA intrinsics.

Originally created by @Rachmanino on GitHub (Jun 12, 2026). Original GitHub issue: https://github.com/deepseek-ai/DeepGEMM/issues/358 DeepGEMM already has a CMake path intended for IDE indexing, but clangd setup is currently not straightforward for CUDA headers. In my local setup I needed: - a dedicated `build-clangd` directory with `CMAKE_EXPORT_COMPILE_COMMANDS=ON` - `pybind11`/Torch CMake prefixes passed explicitly - `.clangd` CUDA flags for `.cuh` files, e.g. `-x cuda`, `--cuda-gpu-arch=sm_100`, `--cuda-path=...` - removal of some nvcc-only flags - a few diagnostic suppressions for CUDA 13.x / SM100 false positives Would the project be open to adding either: 1. a short clangd setup section in the README, or 2. a helper script such as `scripts/configure_clangd.sh`, or 3. a checked-in template `.clangd.example`? The goal would be reliable navigation/indexing for kernel development, not necessarily zero clang diagnostics for all CUDA intrinsics.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
public-sync-20261014
0930-release
nv_dev
fix-mega-moe-fence
public-release-2609
public-release-2607
public-release-2606
mega-update
public-release-260416
ko3n1g/ci/build-wheels
nv_dev_f8e8fb5
nv_dev_950d31a
nv_dev_67fc648
nv_dev_c491439
nv_dev_4ff3f54
v2.1.1.post3
v2.1.1.post2
v2.1.1.post1
v2.1.1
v2.1.0
Labels
Clear labels   
pull-request
Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepGEMM#169
No description provided.