mirror of
https://github.com/deepseek-ai/DeepGEMM.git
synced 2026-11-05 00:47:26 +00:00
[PR #403] Fix SM120 scale-factor layout transformation #421
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepGEMM#421
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/deepseek-ai/DeepGEMM/pull/403
Author: @bvolpato
Created: 8/8/2026
Status: 🔄 Open
Base:
main← Head:bvolpato/fix-sm120-sf-layout📝 Commits (1)
9ac2b5bFix SM120 scale-factor layout transformation📊 Changes
2 files changed (+33 additions, -4 deletions)
View changed files
📝
csrc/apis/layout.hpp(+4 -4)📝
tests/test_layout.py(+29 -0)📄 Description
Summary
Addresses #372 by allowing explicit SM120 scale-factor recipes to use the existing SM100 UE8M0 packing and packed-scale validation paths. The same architecture support is already present in
nv_dev.Default recipes, K-grouped layouts, and broader SM120 inference support are outside this change. SM121 has not been tested.
Reproduction
On
mainat057ca59, this fails on an RTX 5070 Ti withUnknown SF transformation:With the patch, it returns packed
torch.int32scales with shape(4, 128, 2)and stride(256, 1, 128).Testing
The build, reproduction, and layout checks passed on an RTX 5070 Ti with CUDA 13.2 and PyTorch 2.13.0+cu130:
DG_USE_NVIDIA_TOOLS=1skips profiling while keeping correctness checks enabled; SM100-only cases did not run on this GPU. Builds used locally supplied elfutils development headers, andgit diff --checkpassed.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.