All problems in computer science can be solved by another level of indirection
Using PLT trampolines to provide a BLAS and LAPACK demuxing library. Watch a detailed JuliaCon 2021 talk on libblastrampoline.
These BLAS libraries are known to work with libblastrampoline (successfully tested in Julia):
Build libblastrampoline.so, then link your BLAS-using library against it instead of libblas.so.
When libblastrampoline is loaded, it will inspect the LBT_DEFAULT_LIBS environment variable and attempt to forward BLAS calls made to it on to that library (this can be a list of semicolon-separated libraries if your backing implementation is split across multiple libraries, such as in the case of separate BLAS and LAPACK libraries).
If LBT_DEFAULT_LIBS is not set, then libblastrampoline will fall back to the definition of the LBT_FALLBACK_LIBS macro specified at compile time.
At any time, you may call lbt_forward(libname, clear, verbose) to redirect forwarding to a new BLAS library.
If you set clear to 1 it will clear out all previous mappings before setting new mappings, while if it is set to 0 it will leave symbols that do not exist within the given libname alone.
This is used to implement layering of libraries, such as between a split BLAS and LAPACK library:
lbt_forward("libblas.so", 1, 0);
lbt_forward("liblapack.so", 0, 0);libblastrampoline exports a consistent ABI for applications to link against.
In particular, we export both a 32-bit (LP64) and 64-bit (ILP64) interface, allowing applications that use one or the other (or both!) to link against the library.
Applications that wish to use the 64-bit interface must append _64 to their function calls, e.g. instead of calling dgemm() they must call dgemm_64().
The BLAS/LAPACK symbol list we re-export comes from the gensymbol script contained within OpenBLAS.
See ext/gensymbol for more.
We note that we have an experimental Clang.jl-based symbol extractor that extracts only those symbols that are defined within the headers shipped with OpenBLAS, however as there are hundreds of symbols that gensymbol knows about (and are indeed exported from the shared library libopenblas.so) that are not included in the public C headers, we take the conservative approach and export the gensymbol-sourced symbols.
Because we export both the 32-bit (LP64) and 64-bit (ILP64) interfaces, if clients need header files defining the various BLAS/LAPACK functions, they must include headers defining the appropriate ABI.
We provide headers broken down by interface (LP64 vs. ILP64) as well as target (e.g. x86_64-linux-gnu), so to properly compile your code with headers provided by libblastrampoline you must add the appropriate -I${prefix}/include/${interface}/${target} flags.
When libblastrampoline loads a BLAS/LAPACK library, it will inspect it to determine whether it is a 32-bit (LP64) or 64-bit (ILP64) library, and depending on the result, it will forward from its own 32-bit/64-bit names to the names declared in the library its forwarding to.
This allows automatic usage of multiple libraries with different interfaces but the same symbol names.
libblastrampoline is also cognizant of the f2c calling convention incompatibilities introduced by some libraries such as Apple's Accelerate.
It will automatically probe the library to determine its calling convention and employ a return-value conversion routine to fix the float/double return value differences.
This support is only available on the x86_64 and i686 architectures, however these are the only systems on which the incompatibilty exists to our knowledge.
libblastrampoline-specific APIlibblastrampoline exports a simple configuration API including lbt_forward(), lbt_get_config(), lbt_{set,get}_num_threads(), and more.
Vendor-specific APIs such as openblas_get_num_threads() are not included in header files or exported from the library.
See the public header file for the most up-to-date documentation on the libblastrampoline API.
Note: all lbt_* functions should be considered thread-unsafe.
Do not attempt to load two BLAS libraries on two different threads at the same time.
This library has the ability to work with a mixture of LP64 and ILP64 BLAS libraries, but is slightly hampered on certain platforms that do not have the capability to perform RTLD_DEEPBIND-style linking.
As of the time of this writing, this includes FreeBSD and musl Linux.
The impact of this is that you are unable to load an ILP64 BLAS that exports the typical LP64 names (e.g. dgemm_) at the same time as an actual LP64 BLAS (with any naming scheme).
This is because without RTLD_DEEPBIND-style linking semantics, when the ILP64 BLAS tries to call one of its own functions, it will call the function exported by libblastrampoline itself, which will result in incorrect values and segfaults.
To address this, libblastrampoline will detect if you attempt to do this and refuse to load a library that would cause this kind of confusion.
You can always tell if your system is limited in this fashion by calling lbt_get_config() and checking the build_flags member for the LBT_BUILDFLAGS_DEEPBINDLESS flag.