-
Notifications
You must be signed in to change notification settings - Fork 7
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
Compile all backends without auto-detection #13
Comments
The fun fact is, that there is no need to have them at compile time. Just create a file
and check with The so-file have to contain the a normal NETLIB compatible BLAS interface and must include all its dependencies. If a BLAS symbols does not exists in the so-file it is automatically replaced by its NETLIB implementation. For ATLAS that means you need the combined so as installed by Debian/Ubuntu as
For OpenBLAS, just use the generated so file. For BLIS, just use the generated so file, but it have to be compiled with the BLAS wrapper layer. (config option: In case of the MKL its a bit tricky, since it consits of at least three so files that have to be combined such that they fit your requirements. Therefore, Intel provides a tool called mklbuilder. In my installation it is located in
One can generate such an so-file which includes the sequential version of the MKL as a single so file. This can be used in the config files. (The For fast tests is is enought to set the the As long as the names in the configfiles are unique, many different BLAS libraries of the same vendor could be defined. I use this to switch between OpenBLAS in sequential and OpenMP mode while developing software. Does this help? I think I write a short readme in the next release abou this. |
Yes, this was very informative! Thanks a lot!
I'd really appreciate this as well, thanks! ❤️ |
Then I close this issue and some information on this will appear in the next release. |
How would I compile flexiblas with support for all ATLAS, OpenBLAS, MKL and BLIS while not having them present at compile time?
Thanks a lot!!
The text was updated successfully, but these errors were encountered: