Skip to content
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

compute type of hipblasGemmEx #753

Closed
jinz2014 opened this issue Dec 21, 2023 · 2 comments
Closed

compute type of hipblasGemmEx #753

jinz2014 opened this issue Dec 21, 2023 · 2 comments
Assignees

Comments

@jinz2014
Copy link

Running a CUDA program shows that cublasGemmEx supports compute type CUBLAS_COMPUTE_32F_FAST_TF32 and CUBLAS_GEMM_DEFAULT_TENSOR_OP. The type is not available in hipBLAS. Thank you for your discussion.

status = cublasGemmEx(handle, CUBLAS_OP_N, CUBLAS_OP_N, B_cols, A_rows, A_cols, &alpha, gpu_B, CUDA_R_32F, A_rows, gpu_A, CUDA_R_32F,
                      A_cols, &beta, gpu_C, CUDA_R_32F, A_rows, CUBLAS_COMPUTE_32F_FAST_TF32, CUBLAS_GEMM_DEFAULT_TENSOR_OP);
@daineAMD
Copy link
Contributor

Hi @jinz2014,

hipblasComputeType_t was added for the ROCm 6.0.0 release, and includes HIPBLAS_COMPUTE_32F_FAST_TF32 which is the equivalent of CUBLAS_COMPUTE_32F_FAST_TF32. Note that rocBLAS does not have an equivalent computeType so will return HIPBLAS_STATUS_NOT_SUPPORTED if used with the rocBLAS backend.
Note that hipblasComputeType_t is only used with the HIPBLAS_V2 API for now while the old interface for hipblasGemmEx is deprecated. You can take a look at some documentation on the HIPBLAS_V2 API, along with hipblasGemmEx documentation. At some point in the future the hipblasComputeType_t version of hipblasGemmEx will be standard.

CUBLAS_GEMM_DEFAULT_TENSOR_OP is deprecated in cuBLAS, I will discuss with the team if we believe it should be added to the library.

Thanks,
Daine

@daineAMD
Copy link
Contributor

Hi again @jinz2014,

I hope the HIPBLAS_V2 API was able to satisfy your needs regarding the compute types for gemmEx. Again, this will be the default behaviour of hipBLAS in the future, but for now it lives within the HIPBLAS_V2 API.

If you have any further questions feel free to re-open this issue or open another.

Thanks,
Daine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants