-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update matmul.md #2203
base: main
Are you sure you want to change the base?
Update matmul.md #2203
Conversation
updated supported data types
Thanks for the PR. Could you please rename the commit message to adhere to the oneDNN coding guideline. |
@mgouicem message updated. thanks. |
@@ -188,6 +189,7 @@ memory buffer that shares its shape with the destination buffer). | |||
* Runtime dimensions. | |||
* Three and higher dimensional matrices. | |||
- The layout of dropout mask has to be exactly the same as that of dst. | |||
- f64 is only supported on Intel(R) Data Center GPU Max Series. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There might be other platforms supporting f64 in the future, it would be better not to mention this specific platform and align with the description in dev_guide_data_types.html:
f64 configurations are only supported on GPU engines with HW capability for double-precision floating-point.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor edits suggested. Please incorporate as you see fit! Thanks!
@@ -67,7 +67,7 @@ argument index as specified by the following table. | |||
user must pass fully specified memory objects so that the primitive is able | |||
to perform the computations. Note that the less information about shapes | |||
or format is available at the creation stage, the less performant execution | |||
will be. In particular, if the shape is not known at creation stage, one | |||
will be. In particular, if the shape is not known at the creation stage, one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will be. In particular, if the shape is not known at the creation stage, one | |
will be. In particular, if the shape is not known at the creation stage, you |
@@ -80,13 +80,13 @@ argument index as specified by the following table. | |||
invalid. | |||
|
|||
3. The broadcasting shape consistency check is not done for the dimensions with | |||
#DNNL_RUNTIME_DIM_VAL. It is user responsibility to make sure the dimensions | |||
#DNNL_RUNTIME_DIM_VAL. It is the user's responsibility to make sure the dimensions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#DNNL_RUNTIME_DIM_VAL. It is the user's responsibility to make sure the dimensions | |
#DNNL_RUNTIME_DIM_VAL. Make sure the dimensions |
for the tensors are valid. | ||
|
||
4. Multiple batch dimensions and broadcasting of batch dimensions of `src` and | ||
`weights` are supported for both CPU and GPU engines. | ||
|
||
Please check tutorials below to see #DNNL_RUNTIME_DIM_VAL support in use. | ||
Please check the tutorials below to see #DNNL_RUNTIME_DIM_VAL support in use. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please check the tutorials below to see #DNNL_RUNTIME_DIM_VAL support in use. | |
Check the tutorials below to see #DNNL_RUNTIME_DIM_VAL support in use. |
doc: matmul: updated supported data types