-
Notifications
You must be signed in to change notification settings - Fork 23
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
Move [cz]symv and [cz]syr from LAPACK++ #91
base: master
Are you sure you want to change the base?
Conversation
@weslleyspereira Related to earlier discussion in PR #11. |
…are defined in LAPACK, not in reference BLAS, so require a full LAPACK.
`string( REGEX MATCH pattern x str )` as simpler and more robust than `if (pattern MATCHES str) set( x true ) endif` To be robust when x is already defined, that would need `else set( x false )`.
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.
Reviewed.
test/test_symv.cc
Outdated
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.
Add to test.hh
and test.cc
.
Add to run_tests.py
.
Compare with icl-utk-edu/lapackpp#71.
This moves
[cz]symv
and[cz]syr
into BLAS++, where they logically should reside, rather than LAPACK++, where they have resided for historical reasons.[cz]symv
and[cz]syr
are in LAPACK rather than Reference BLAS. Most vendors ship BLAS and LAPACK together (OpenBLAS, Intel MKL, Cray LibSci), so users don't notice the difference.However, IBM ESSL notably has only a limited subset of LAPACK, and lacks
[cz]symv
and[cz]syr
. For ESSL, users can also link with reference LAPACK to complete it. See https://www.ibm.com/docs/en/essl/6.3?topic=reference-lapack-lapacke.This supersedes PR #86.