Default BLAS/LAPACK implementation + runtime exchangeable backends

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I didn't find this proposal in the archives, so let me add something
to this discussion. Does anyone know about FlexiBLAS [1]? It seems
like the perfect solution to this problem, and AFAIK, only Arch
packages it. Here's a presentation [2] about it (not up-to-date with
the current feature-set, but still interesting).

TL;DR, the general idea would be to build everything in Fedora against
the libblas.so, liblapack.so and libumfpack.so wrappers provided by
FlexiBLAS, and then it redirects the calls to the proper library (that
could be openblas-serial by default, of course). Then it provides the
user with a nice mechanism to select a backend (not based on
update-alternatives, no root privileges required). Additionally, it
embeds some profiling capabilities, which is really nice.

I think it's very much worth a try. Opinions?

[1] https://www.mpi-magdeburg.mpg.de/projects/flexiblas
[2] https://www2.mpi-magdeburg.mpg.de/mpcsc/software/flexiblas/2018_talk_fin_flexiblas.pdf

-- 
Iñaki Úcar
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux