Doc only change to CUTLASS 3.3 changelog #1180
Merged
Conversation
This file contains 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
manishucsd
force-pushed
the
doc_only_change_changelog_3.3
branch
from
2e578f9 to
a87fb92
Compare
|
could you pleae also change CHANGELOG.md? |
manishucsd
force-pushed
the
doc_only_change_changelog_3.3
branch
from
a87fb92 to
56fb032
Compare
done |
hwu36
approved these changes
Nov 13, 2023
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.
This doc-only PR addresses the discussion at #1170
Summary and rationale for the suggested changes
Mixed-PrecisiontoMixed-Input.Mixed-Precisionis taken by the GEMM data-type where inputs (DataType(operandA) == DataType(operandB) are mixed with a different accumulation data type (F16*F16+F32andBF16*BF16+F32). The code uses cutlass::arch::OpMultiplyAddMixedInputUpcast tag to navigate and communicate that input data types are mixed. It would be good to set a nomenclature that is consistent and distinguishes betweenMixed-PrecisionandMixed-Inputuse-case.Update the hyperlink for
Mixed Precision Ampere GEMMsto the PR#1084 which has detailed description, steps to only compile Ampere mixed-input GEMMs, reproduce performance results, and a performance graph.