Skip to content

Conversation

@sempervictus
Copy link

@sempervictus sempervictus commented Jan 26, 2026

Cutlass needs to know about SM120a to properly build certain code such sa block-scaled MMA and FP4 related components ( NVIDIA/cutlass#2820
pytorch/pytorch#172807
).

Attempt to remedy this by allowing the parser to detect the digits of the compute cap returned by smi or taken from the env when the default parse fails by dropping the last char of the parsed string. Record the provided cap in the environment variable target to pass it downstream but retain the usize datatype for this library for now.

Cutlass needs to know about SM120a to properly build certain code
such sa block-scaled MMA and FP4 relates components (
NVIDIA/cutlass#2820
pytorch/pytorch#172807
).

Attempt to remedy this by allowing the parser to detect the digits
of the compute cap returned by smi or taken from the env when the
default parse fails by dropping the last char of the parsed string.
Record the provided cap in the environment variable target to pass
it downstream but retain the usize datatype for this library for
now.
compute_cap_str
.parse::<usize>()
.expect("Could not parse code")
match compute_cap_str.parse::<usize>() {
Copy link
Owner

Choose a reason for hiding this comment

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

Maybe we should just parse into its own type ?

Copy link
Author

Choose a reason for hiding this comment

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

Yes that would be the proper fix, I did a quick grep for users and didn't quite have time to validate interface sanity for such a change so threw this up as a quickie "fix"

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