Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
About the convergence, I actually want to separate out the low-level backend interface from the high level user interface. That way, multiple high level libraries can employ the same common low-level backends. This has been my motivation for CL-CBLAS and CL-BMAS.
Is there a canonical (C)BLAS header file? I've been using the one provided by netlib, however OpenBLAS also provides a cblas.h and this also defines some additional functions such as cblas_crotg and cblas_zrotg. What about versioning for header files?
I don't see awesome-cl listing anything for fortran interface. Does that mean I should be sticking only to CBLAS and ignore Fortran or other versions altogether? I have only worked a bit with C, and not even extensively; and never with Fortran. Are Fortran libraries used through lisp/cffi in the wild?
About the convergence, I actually want to separate out the low-level backend interface from the high level user interface. That way, multiple high level libraries can employ the same common low-level backends. This has been my motivation for CL-CBLAS and CL-BMAS.
I agree... and I do don't want be the person who has not rallied. I just took a look at guicho's issue from 2019. And here, you yourself have admitted that the high level interface is less than ideal and needs more work. However, the very point that magicl is an industry standard could imply that potentially radical backward-incompatible changes can be hard. But, honestly, I want to discuss this, time permitting!