Refresh CUDA 13.4 bindings (cybind !561, !574, !580)

[rwgk]

Description

Regenerate the CUDA 13.4 bindings using cybind MR !580.

Supersedes #2950.

All changed files are generated; none was edited by hand.

This refresh brings in three behavior changes:

• Embedded driver and runtime struct/union wrappers now retain their parent while pointing into its C storage. This fixes dangling child pointers when a caller keeps a child after dropping its parent. — cybind !574 88a61d6d, 3ac802c4
• Twenty-two driver/runtime pointer-array getters now return copies of the top-level structs instead of wrappers pointing into the parent's array. Saved elements therefore survive a parent-array resize or release. This changes write-through behavior: modifying a returned element no longer changes the parent array; callers must assign the modified array back. Pointers inside a copied struct are still shallow copies. — cybind !574 88a61d6d, 3ac802c4
• nvml.NvlinkFirmwareInfo.firmware_version now exposes only numValidEntries elements rather than all 100 slots. Its setter accepts up to 100 elements and sets the count automatically. The generated num_valid_entries Python property (including its setter) is removed. — cybind !561 a7b0b86a

Compatibility review

The first fix adds _owner fields to 241 public Cython cdef class declarations; regeneration also adds two fields to CUmemDecompressParams_st. These declarations change extension-type layouts. The cuda.bindings support policy exposes the Cython cimport layer and warns that a new minor release may require downstream rebuilds. The repository's ABI checker treats changed class sizes and fields as errors. If these bindings are released as a 13.4.x patch, please assess whether prebuilt Cython consumers can continue using them or whether this fix needs an ABI-preserving approach or a minor release.

The pointer-array getters' change from live views to copies and removal of NvlinkFirmwareInfo.num_valid_entries also need Python API compatibility review for a patch release. The latter is an additional effect of regeneration, not part of the two driver/runtime lifetime fixes.

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[rwgk]

/ok to test 20f1320

[github-actions]

Doc Preview CI
Preview removed because the pull request was closed or merged.

[rwgk]

/ok to test 6f04788

[mdboom]

All of the ABI breakage in this PR is at the lowpp layer, for which we make no ABI guarantees. The ABI breakage is real, but it's in service of fixing a real use-after-free pitfall that should be fixed. The policy the agent is referring to is:

The module exposes a Cython layer from which types and functions could be cimport'd. While we strive to keep this layer stable, due to Cython limitations a new minor release of this module could require Cython layer users to rebuild their projects and update their pinning to this module.

I can see how it's confused by Cython layer here -- it doesn't mean all Cython code, it specifically means cydriver.pxd etc., vs. driver.pxd.

As for this, this is an API change, but required for a bugfix:

The pointer-array getters' change from live views to copies and removal of NvlinkFirmwareInfo.num_valid_entries also need Python API compatibility review for a patch release. The latter is an additional effect of regeneration, not part of the two driver/runtime lifetime fixes.

We should add a breaking change note for this (I'll push another commit here).