Add sparse marlin 2:4 gemm op#733
Merged
Merged
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/733
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 8699877 with merge base 0ed3090 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
jcaip
approved these changes
Aug 23, 2024
Contributor
|
that was fast haha, 1 shot green ci ;) |
Contributor
Author
|
Glad I could be of help! |
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
4 participants
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
This PR is a more concise version of #621 where only the gemm op and surrounding functions are implemented for a 2:4 sparse marlin kernel.
What was done:
opcheck()to check iftorch.compilewill work out of the box with itdequantize()is called)Notes:
cc @jcaip