-
Notifications
You must be signed in to change notification settings - Fork 36
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
Bias and more metadata in gradlib and tuned gemm #202
Conversation
… bias and dtype captured from the actual capture run
… fp8 with bias (future proof)
I recall for fp16 gemm, rocblas solutions are also queried. Does this PR make the change for rocblas part of gradlib? |
Only so that if a gemm is tuned with bias, times for rocblas are computed while adding bias separately. |
* Adding bias to hipb_mm in gradlib. Expanding gradlib to tune based on bias and dtype captured from the actual capture run
Using hipblaslt solutions with bias support for gemms with bias. Comparing them against rocblas with separate bias add for fair comparison.
Writing bias, in dtype, out dtype in the untuned and tuned file to reuse the same tuned csv.
dtypes can be overriden by the command line to tune for fp8