Skip to content

Commit 0b8d155

Browse files
committed
update
1 parent 085133b commit 0b8d155

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

cuda_core/docs/source/release/0.1.1-notes.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# `cuda.core` v0.1.1 Release notes
22

3-
Released on Dec XX, 2024
3+
Released on Dec 20, 2024
44

55
## Hightlights
66

@@ -9,11 +9,11 @@ Released on Dec XX, 2024
99
- Add `Linker` that can link one or multiple `ObjectCode` instances generated by `Program`s. Under
1010
the hood, it uses either the nvJitLink or driver (`cuLink*`) APIs depending on the CUDA version
1111
detected in the current environment.
12-
- Add a `cuda.core.experimental.system` module for querying system- or process- wide information.
1312
- Support `pip install cuda-core`. Please see the Installation Guide for further detail.
1413

1514
## New features
1615

16+
- Add a `cuda.core.experimental.system` module for querying system- or process- wide information.
1717
- Add `LaunchConfig.cluster` to support thread block clusters on Hopper GPUs.
1818

1919
## Enchancements
@@ -38,4 +38,6 @@ Released on Dec XX, 2024
3838
not supported. This will be fixed in a future release.
3939
- Some `LinkerOptions` are only available when using a modern version of CUDA. When using CUDA <12,
4040
the backend is the cuLink api which supports only a subset of the options that nvjitlink does.
41-
Further, some options aren't available on CUDA versions <12.6
41+
Further, some options aren't available on CUDA versions <12.6.
42+
- To use `cuda.core` with Python 3.13, it currently requires building `cuda-python` from source
43+
prior to `pip install`. This extra step will be fixed soon.

0 commit comments

Comments
 (0)