Skip to content

Fix BLAS, BLAS-like functions and Generic RISC-V kernels #4452

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

Merged
merged 8 commits into from
Jan 24, 2024

Conversation

kseniyazaytseva
Copy link
Contributor

  • Fixed gemmt: Added explicit declarations of gemmt functions. Fixed problems associated with incorrect processing of complex conjugate matrices. Error output has also been corrected.
  • Fixed CNC case of zimatcopy functions. In the case of alpha_r = 1.0 alpha_i = 0.0, need to perform the usual complex matrix conjugation
  • Fixed imatcopy function memory allocation
  • Fixed calling cblas_cscal testing in ctest
  • Removed rotmg unreacheble code
  • Added zero size checks
  • Added axpby kernels for GENERIC RISC-V target

@martin-frbg
Copy link
Collaborator

Thanks - I believe that several of these were already fixed in the main develop branch in the rather (too) long time since the risc-v branch was created. Did you check ?

@kseniyazaytseva
Copy link
Contributor Author

kseniyazaytseva commented Jan 24, 2024

Yes, the files riscv64/dot.c and interface/imatcopy.c have been fixed in the develop branch, as I see

For gemmt there are still no explicit declarations. The file interface/gemmt.c in develop was modified several times, these changes are merged to the PR. But the main problem with incorrect processing of complex conjugate matrices wasn't fixed.

@martin-frbg
Copy link
Collaborator

Ah thanks, that's unfortunate - seems I never commited the changes to cblas.h - and there's no question that the implementation of the complex conjugate case is/was broken.

@martin-frbg
Copy link
Collaborator

BTW the CSCAL/CSCALTEST confusion in c_cblat1.f appears to be imported from https://github.com/Reference-LAPACK/lapack/blame/master/CBLAS/testing/c_cblat1.f - I wonder if you would like to open a PR there as well ?

@kseniyazaytseva
Copy link
Contributor Author

I agree that it should probably be fixed in Reference-LAPACK. But I'm just focused on OpenBLAS

@martin-frbg
Copy link
Collaborator

I can create an issue/PR in Reference-LAPACK no problem - I just wanted to make sure you do not want to do this yourself.

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

Successfully merging this pull request may close these issues.

2 participants