You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just wanted to check whether blis considers itself compatible with the BLAS APIs from upstream 3.10.1. We'd like to lift our baseline across blas-flavours in conda-forge, and for that I'd like to make sure that all symbols are supported everywhere. Perhaps this is a wrong question to ask, given blis' architecture, but I cannot really tell the state as an outsider. 😅
I would say the we general do not claim to have full compatibility with the reference BLAS APIs, but that we strive to correct any inconsistencies when they are brought to our attention. For example we recently fixed some errors related to NaN/Inf handling in the level 1 routines. If you notice anything else please bring it to our attention.
We also run the BLAS testsuite as part of our CI process. We could update the version of the testsuite included if there are important changes.
Hey all
I just wanted to check whether blis considers itself compatible with the BLAS APIs from upstream 3.10.1. We'd like to lift our baseline across blas-flavours in conda-forge, and for that I'd like to make sure that all symbols are supported everywhere. Perhaps this is a wrong question to ask, given blis' architecture, but I cannot really tell the state as an outsider. 😅
For reference, running
on the upstream repo I get the following stats:
The text was updated successfully, but these errors were encountered: