cuda-bindings 13.4.3 Release notes#
Bugfixes#
Fixed the internal result storage and Python conversion for several
CUpointer_attributeandCUcoredumpSettingsresult types:CU_POINTER_ATTRIBUTE_DEVICE_ORDINALis now returned from signed integer storage so negative CUDA device sentinels are preserved,CU_POINTER_ATTRIBUTE_ALLOWED_HANDLE_TYPESis stored in its 64-bit unsigned slot instead of being truncated to 32 bits,CU_POINTER_ATTRIBUTE_HOST_POINTERuses avoid *result slot, and the boolean coredump attributes use a one-byteboolmatching the driver ABI. (PR #2929)Fixed
CU_JIT_WALL_TIMEandcudaJitWallTimeOUT slots: the pointer passed to the driver is now the address of the float storage cell instead of the float bit-pattern value-cast to a pointer, which previously produced a garbage address that could crash or corrupt memory when CUDA wrote back the elapsed time. (PR #2931)Added missing helper branches for
CUpointer_attribute,CUmemPool_attribute,CUmem_range_attribute,CUjit_optionandCUcoredumpSettingsenumerators that previously raisedTypeErrorat construction time. (PR #2931)Added missing
getDescInfoandgetChannelFormatDescFromDriverDescarms for the{Signed,Unsigned}Normalized{8,16}X{1,2,4}channel kinds and for the CUDA 13.3 / 13.4 packed and multi-planar YUV channel kinds, which previously returnedcudaErrorInvalidChannelDescriptor. (PR #2931)
Known issues#
Updating from older versions (v12.6.2.post1 and below) via
pip install -U cuda-pythonmight not work. Please do a clean re-installation by uninstallingpip uninstall -y cuda-pythonfollowed by installingpip install cuda-python.nvml.system_get_process_nameon WSL can return incorrect values. To work around this, set the locale to “C” before callingnvml.device_get_compute_running_processes_v3(which sets the process names) and before callingnvml.system_get_process_name.cuda_coredoes this automatically, but users of the raw NVML API will need to do this manually.