Is this a duplicate?
Area
cuda.core
Is your feature request related to a problem? Please describe.
LaunchConfig does not expose CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENT, which records a programmatic event for cross-stream PDL (complements same-stream programmatic_stream_serialization from #1334).
Parent tracking: #496.
Describe the solution you'd like
Describe alternatives you've considered
Use cuda.bindings.driver (CUlaunchAttribute / CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENT) and cuLaunchKernelEx directly.
Downside: leaves cuda.core users without a first-class LaunchConfig API; they must drop to low-level bindings, manage the attribute array themselves, and lose consistency with other LaunchConfig launch attributes (programmatic_stream_serialization, etc.).
Additional context
Incremental LaunchConfig attribute coverage under #496 (same approach as #1334 for programmatic_stream_serialization).
No example code in the design notes for this attribute.
Is this a duplicate?
Area
cuda.core
Is your feature request related to a problem? Please describe.
LaunchConfigdoes not exposeCU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENT, which records a programmatic event for cross-stream PDL (complements same-streamprogrammatic_stream_serializationfrom #1334).Parent tracking: #496.
Describe the solution you'd like
CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENTviaLaunchConfig.Describe alternatives you've considered
Use
cuda.bindings.driver(CUlaunchAttribute/CU_LAUNCH_ATTRIBUTE_PROGRAMMATIC_EVENT) andcuLaunchKernelExdirectly.Downside: leaves
cuda.coreusers without a first-classLaunchConfigAPI; they must drop to low-level bindings, manage the attribute array themselves, and lose consistency with otherLaunchConfiglaunch attributes (programmatic_stream_serialization, etc.).Additional context
Incremental
LaunchConfigattribute coverage under #496 (same approach as #1334 forprogrammatic_stream_serialization).No example code in the design notes for this attribute.