Skip to content

python3Packages.nvidia-cutlass-dsl: 4.3.0 -> 4.4.1#335

Merged
danieldk merged 5 commits intomainfrom
cutlass-dsl-4.4.1
Mar 12, 2026
Merged

python3Packages.nvidia-cutlass-dsl: 4.3.0 -> 4.4.1#335
danieldk merged 5 commits intomainfrom
cutlass-dsl-4.4.1

Conversation

@danieldk
Copy link
Member

No description provided.


meta = {
broken = !(cudaPackages.cudaAtLeast "12.8");
broken = nvidia-cutlass-dsl-libs.meta.broken;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow, this is quite cool!

buildPythonPackage rec {
pname = "nvidia-cutlass-dsl";
version = "4.3.0";
version = "4.4.1";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pardon my unwisdom but is this sufficiently BW-compatible?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so, kernels using this are going to use this as a Python API, so it's kind of similar to how we handle Triton or Torch Python dependencies (i.e. not at all 😅, it's up to kernels to check the version and have specific code paths if they want to support old Triton/Torch versions). In this case, I think there isn't going to be any breakage at all, because most kernel couldn't use this yet, since JIT-ing was broken in cutlass-dsl in kernels due to not supporting relative imports (fixed in 4.4).

@danieldk danieldk merged commit ab6917a into main Mar 12, 2026
38 checks passed
@danieldk danieldk deleted the cutlass-dsl-4.4.1 branch March 12, 2026 14:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants