Basil Milanich d36ca27041 Fix graph correlation: use shared correlationId, not GRAPH_TRACE ...

CUPTI discovery: all kernels launched by one cuGraphLaunch share the
same correlationId as the launch call itself. GRAPH_TRACE was the
wrong approach — enabling it suppresses per-kernel CONCURRENT_KERNEL
records entirely, replacing them with graph-level summaries.

New approach:
- Drop CUPTI_ACTIVITY_KIND_GRAPH_TRACE (it conflicts with CONCURRENT_KERNEL)
- Drop two-pass buffer processing (no longer needed)
- On the first kernel/memcpy/memset from a graph launch, matchActivityToAPICall
  succeeds (consuming the cuGraphLaunch entry) and the result is cached in
  cudaGraphCurrentLaunch[graphId]
- Subsequent operations from the same launch find the cached entry via graphId

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-06 11:36:14 -05:00

..

client

Windows x64 vs ARM opsie

2026-03-09 13:24:08 -07:00

common

clang visibility for TRACY_API (#1310)

2026-03-18 23:59:33 +01:00

libbacktrace

fix: GetDebugInfoDescriptor signature

2025-11-13 19:19:52 +02:00

tracy

Fix graph correlation: use shared correlationId, not GRAPH_TRACE

2026-04-06 11:36:14 -05:00

TracyClient.cpp

Refactor libbacktrace usage with TRACY_USE_LIBBACKTRACE

2025-07-31 10:41:37 +02:00

TracyClient.F90

Fix type(c_ptr) in bind(C)

2025-01-05 23:21:12 +01:00