-
Notifications
You must be signed in to change notification settings - Fork 43
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
8 test failures against openblas #367
Comments
From your log:
At first glance, half those failures appear to be minor differences in precision (/18). The other half will require more investigation (/16). |
Hi @littlewu2508. It appears that this issue has been resolved in recent versions of rocSOLVER. I managed to reproduce these test failures using rocSOLVER for rocm-4.3.0 with OpenBLAS 0.3.19. However, when I tried with rocSOLVER for rocm-4.5.2 and rocm-5.1.1 (still with OpenBLAS 0.3.19), the tests all passed. In fact, when I updated to OpenBLAS 0.3.20 (for the laswp fix you helped with), rocSOLVER for rocm-5.1.1 passed the full test suite! |
That's brilliant, I'll test the rocSOLVER rocm-5.x. It would be perfect if fix can be backported to 4.3.x. Many users stick to 4.3.x version because they use older cards like Fury. |
A new 4.3.x release is unlikely, but if you're compiling from source, you could build newer versions of rocBLAS/rocSOLVER on older versions of the rocm-dev stack. I know for a fact that the versions of rocBLAS and rocSOLVER tagged at rocm-4.5.2 will build using the HIP stack from ROCm 4.3.1. In fact, I think you can probably build the versions of rocBLAS and rocSOLVER tagged at rocm-5.1.1 with the HIP stack from ROCm 4.3.1. Just be sure to rebuild all the {roc,hip}{BLAS,SOLVER} libraries at the new tag, since they all use private (unstable) APIs provided by rocBLAS. |
Thanks for pointing out! |
Just to confirm. Yes, this is possible. |
According to ROCm/rocSOLVER#367 (comment) hip and low-level runtimes of rocm does not need to be the same version with high-level libraries. Loosen dev-util/hip SLOT dependencies Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Yiyang Wu <xgreenlandforwyy@gmail.com>
According to ROCm/rocSOLVER#367 (comment) hip and low-level runtimes of rocm does not need to be the same version with high-level libraries. Loosen dev-util/hip SLOT dependencies Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Yiyang Wu <xgreenlandforwyy@gmail.com>
I tested rocSOLVER-rocm-5.0.2 against openblas-0.3.20 on Radeon RX 6700XT, and all tests have passed. Thanks! |
According to ROCm/rocSOLVER#367 (comment) hip and low-level runtimes of rocm does not need to be the same version with high-level libraries. Loosen dev-util/hip SLOT dependencies All tests passed on single Radeon RX 6700XT Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Yiyang Wu <xgreenlandforwyy@gmail.com>
According to ROCm/rocSOLVER#367 (comment) hip and low-level runtimes of rocm does not need to be the same version with high-level libraries. Loosen dev-util/hip SLOT dependencies All tests passed on single Radeon RX 6700XT Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Yiyang Wu <xgreenlandforwyy@gmail.com> Signed-off-by: Benda Xu <heroxbd@gentoo.org>
After resolving OpenMathLib/OpenBLAS#3513 and #363 I performed the test on rocSOLVER-rocm-4.3.0 against openblas-0.3.19, and there are 8 tests failures reported:
with gzip compressed full test log:
rocSOLVER-rocm4.3.0-against-openblas.log.gz
Earlier I have reported 8 tests failed comparing rocBLAS and openblas, maybe they are related with these failures.
Environment
The text was updated successfully, but these errors were encountered: