Structs

\brief The data type the tensor can hold. The data type is assumed to follow the native endian-ness. An explicit error message should be raised when attempting to export an array with non-native endianness
\brief A Device for Tensor and operator.
\brief C Tensor object, manage memory of DLTensor. This data structure is intended to facilitate the borrowing of DLTensor by another framework. It is not meant to transfer the tensor. When the borrowing framework doesn’t need the tensor, it should call the deleter to notify the host that the resource is no longer needed.
\brief Plain C Tensor object, does not manage memory.

Constants

\brief complex number (C/C++/Python layout: compact struct per complex number)
\brief IEEE floating point
\brief signed integer
\brief Opaque handle type, reserved for testing purposes. Frameworks need to agree on the handle data type for the exchange to be well-defined.
\brief unsigned integer
\brief CPU device
\brief CUDA GPU device
\brief Pinned CUDA CPU memory by cudaMallocHost
\brief CUDA managed/unified memory allocated by cudaMallocManaged
\brief Reserved extension device type, used for quickly test extension device The semantics can differ depending on the implementation.
\brief Qualcomm Hexagon DSP
\brief Metal for Apple GPU.
\brief Unified shared memory allocated on a oneAPI non-partititioned device. Call to oneAPI runtime is required to determine the device type, the USM allocation type and the sycl context it is bound to.
\brief OpenCL devices.
\brief ROCm GPUs for AMD GPUs
\brief Pinned ROCm CPU memory allocated by hipMallocHost
\brief Verilog simulator buffer
\brief Vulkan buffer for next generation graphics.
\brief GPU support for next generation WebGPU standard.

Type Definitions