Sparse-checkout from NVIDIA/cccl main branch to complete cccl_upstream: Added: - python/cuda_cccl/ (226 files) — Python bindings for device-level algorithms Critical for muh toolchain: cuda.compute.reduce_into, scan, radix_sort, etc. Includes 204 .py files with full test coverage for all 27 algorithms - ci/ (163 files) — Build/test infrastructure build_cub.sh, test_cub.sh, build_and_test_targets.sh, matrix.yaml Directly maps to our [INFRA-CI] and [INFRA-BUILD] items - .agent/skills/ (7 files) — NVIDIA's own agent skills for CCCL cccl-style/SKILL.md, cccl-test/SKILL.md, sass-diff/SKILL.md - docs/ (491 files) — Official CCCL documentation CI references, CMake guides, Python compute docs, libcudacxx PTX docs - test/ (12 files) — Top-level integration tests (cuda_smoke, stdpar) - Root configs: .clang-format, .clang-tidy, CONTRIBUTING.md, pyproject.toml - CLAUDE.md symlink → AGENTS.md (NVIDIA's standard) cccl_upstream now mirrors full NVIDIA/cccl structure: Before: 42M (cub + thrust + libcudacxx + cudax + c + examples + benchmarks) After: 53M (+python +ci +docs +.agent +test +configs) This completes the CCCL base needed for: - [muh-bench] items: ci/util/build_and_test_targets.sh for targeted builds - [CCCL-verify] items: python/cuda_cccl/tests/ as reference implementations - [CCCL-test] items: ci/test_cub.sh, ci/test_thrust.sh - Agent workflow: .agent/skills/ for consistent style and test patterns
18 lines
932 B
ReStructuredText
18 lines
932 B
ReStructuredText
.. _cub-developer-guide-nvtx:
|
|
|
|
NVTX
|
|
=====
|
|
|
|
The `NVIDIA Tools Extension SDK (NVTX) <https://nvidia.github.io/NVTX/>`_ is a cross-platform API
|
|
for annotating source code to provide contextual information to developer tools.
|
|
All device-scope algorithms in CUB are annotated with NVTX ranges,
|
|
allowing their start and stop to be visualized in profilers
|
|
like `NVIDIA Nsight Systems <https://developer.nvidia.com/nsight-systems>`_.
|
|
Only the public APIs available in the ``<cub/device/device_xxx.cuh>`` headers are annotated,
|
|
excluding direct calls to the dispatch layer.
|
|
NVTX annotations can be disabled by defining ``NVTX_DISABLE`` during compilation.
|
|
When CUB device algorithms are called on a stream subject to
|
|
`graph capture <https://developer.nvidia.com/blog/cuda-graphs/>`_,
|
|
the NVTX range is reported for the duration of capture (where no execution happens),
|
|
and not when a captured graph is executed later (the actual execution).
|