mirror of
https://github.com/deepseek-ai/DeepGEMM.git
synced 2026-11-05 00:47:26 +00:00
[PR #375] Fix non-deterministic results in k_grouped_fp8_gemm_nt_contiguous #397
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#397
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/375
Author: @Functionhx
Created: 7/9/2026
Status: 🔄 Open
Base:
main← Head:fix/fp8-gemm-nondeterministic📝 Commits (1)
4e4e540Fix non-deterministic numerical results in k_grouped_fp8_gemm_nt_contiguous📊 Changes
1 file changed (+10 additions, -7 deletions)
View changed files
📝
deep_gemm/include/deep_gemm/impls/sm90_fp8_gemm_1d1d.cuh(+10 -7)📄 Description
Summary
Fixes #365: non-deterministic numerical results in FP8 grouped GEMM when one expert has exactly 128 tokens.
Root Cause
Race condition in sm90_fp8_gemm_1d1d.cuh: tensormap.replace operations and in-flight TMA data loads were in the same cp.async.bulk commit group. Per PTX ISA, operations within a commit group may complete in any order, allowing descriptor modifications to become visible before pending TMA reads complete.
Fix
Restructure group-switch into three phases:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.