WAR for the cuBLAS grouped gemm issue - #3475
Open
ptrendx wants to merge 1 commit into
Open
Conversation
Signed-off-by: Przemek Tredak <ptredak@nvidia.com>
Contributor
Greptile SummaryThe PR adds a targeted workaround for a cuBLAS 13.7 NVFP4 grouped-GEMM correctness issue on SM103 and SM107.
Confidence Score: 5/5The PR appears safe to merge, with no concrete correctness, compatibility, or security regressions identified. The workaround is limited to affected NVFP4 grouped GEMMs on the specified cuBLAS version and architectures, while existing selection behavior remains intact elsewhere. Important Files Changed
Reviews (1): Last reviewed commit: "WAR for the cuBLAS issue" | Re-trigger Greptile |
Member
Author
|
/te-ci |
1 similar comment
Member
Author
|
/te-ci |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
cuBLAS 13.7 introduced a silent data corruption issue in one of the grouped gemm algorithms on B300 and Rubin. This PR disables this algorithm from being selected.
Type of change
Changes
Please list the changes introduced in this PR:
Checklist: