Skip to content

Commit 4135a2f

Browse files
authored
cuda.core v0.1.1 final doc touch (#301)
* minor changes to the release note * add missing entries * Update 0.1.1-notes.md * update * address comments * mention Python/OS support matrix
1 parent 33b7366 commit 4135a2f

File tree

3 files changed

+18
-11
lines changed

3 files changed

+18
-11
lines changed

‎cuda_core/docs/source/install.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ dependencies are as follows:
1212

1313
[^1]: Including `cuda-python`.
1414

15+
`cuda.core` supports Python 3.9 - 3.12, on Linux (x86-64, arm64) and Windows (x86-64).
16+
1517
## Installing from PyPI
1618

1719
`cuda.core` works with `cuda.bindings` (part of `cuda-python`) 11 or 12. For example with CUDA 12:

‎cuda_core/docs/source/release/0.1.0-notes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# `cuda.core` Release notes
1+
# `cuda.core` v0.1.0 Release notes
22

33
Released on Nov 8, 2024
44

Lines changed: 15 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,28 @@
1-
# `cuda.core` Release notes
1+
# `cuda.core` v0.1.1 Release notes
22

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

55
## Hightlights
66

77
- Add `StridedMemoryView` and `@args_viewable_as_strided_memory` that provide a concrete
88
implementation of DLPack & CUDA Array Interface supports.
9-
- Add `Linker` that can link one or multiple `ObjectCode` instances generated by `Program`s. Under
10-
the hood, it uses either the nvJitLink or cuLink APIs depending on the CUDA version detected
11-
in the current environment.
12-
- Add a `cuda.core.experimental.system` module for querying system- or process- wide information.
13-
- Support TCC devices with a default synchronous memory resource to avoid the use of memory pools
9+
- Add `Linker` that can link one or multiple `ObjectCode` instances generated by `Program`. Under
10+
the hood, it uses either the nvJitLink or driver (`cuLink*`) APIs depending on the CUDA version
11+
detected in the current environment.
12+
- Support `pip install cuda-core`. Please see the Installation Guide for further details.
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
2020

21-
- Ensure "ltoir" is a valid code type to `ObjectCode`.
22-
- Improve test coverage.
21+
- The internal handle held by `ObjectCode` is now lazily initialized upon first touch.
22+
- Support TCC devices with a default synchronous memory resource to avoid the use of memory pools.
23+
- Ensure `"ltoir"` is a valid code type to `ObjectCode`.
24+
- Document the `__cuda_stream__` protocol.
25+
- Improve test coverage & documentation cross-references.
2326
- Enforce code formatting.
2427

2528
## Bug fixes
@@ -35,4 +38,6 @@ Released on Dec XX, 2024
3538
not supported. This will be fixed in a future release.
3639
- Some `LinkerOptions` are only available when using a modern version of CUDA. When using CUDA <12,
3740
the backend is the cuLink api which supports only a subset of the options that nvjitlink does.
38-
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)