You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cuda_bindings/docs/source/overview.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -522,7 +522,7 @@ CUDA objects
522
522
Certain CUDA kernels use native CUDA types as their parameters such as ``cudaTextureObject_t``. These types require special handling since they're neither a primitive ctype nor a custom user type. Since ``cuda.bindings`` exposes each of them as Python classes, they each implement ``getPtr()`` and ``__int__()``. These two callables used to support the NumPy and ctypes approach. The difference between each call is further described under `Tips and Tricks <https://nvidia.github.io/cuda-python/cuda-bindings/latest/tips_and_tricks.html#>`_.
523
523
524
524
For this example, lets use the ``transformKernel`` from
Copy file name to clipboardExpand all lines: cuda_core/docs/source/getting-started.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Example: Compiling and Launching a CUDA kernel
32
32
----------------------------------------------
33
33
34
34
To get a taste for ``cuda.core``, let's walk through a simple example that compiles and launches a vector addition kernel.
35
-
You can find the complete example in `vector_add.py <https://github.com/NVIDIA/cuda-python/blob/|cuda_core_github_ref|/cuda_core/examples/vector_add.py>`_
35
+
You can find the complete example in :cuda-core-example:`vector_add.py`
36
36
and browse the :doc:`examples page <examples>` for the rest of the shipped
37
37
workflows.
38
38
@@ -80,7 +80,7 @@ Note the use of the ``name_expressions`` parameter to the :meth:`Program.compile
80
80
Next, we retrieve the compiled kernel from the CUBIN and prepare the arguments and kernel configuration.
81
81
We're using `CuPy <https://cupy.dev/>`_ arrays as inputs for this example, but
0 commit comments