openblas-src
openblas-src copied to clipboard
Source of BLAS and LAPACK via OpenBLAS
From https://github.com/blas-lapack-rs/openblas-src/pull/92#issuecomment-1345185612 > Currently, openblas-build checks libopenblas.so contains LAPACK symbols because OpenBLAS build system had not built Fortran-based LAPACK routines even if NO_LAPACK is not set. On 0.3.21 this situation...
I would like to run routines such as `sgemm` in a multit-hreaded fashion. So I have done this using `cblas`, but it seems to be single-threaded. I tried changing it...
Hello Team, With openblas static feature, it can be linked statically but the gfortran itself was linked dynamically (gcc -lgfortran was required to link openblas), e.g, libgfortran.so.5 was actually linked...
There was an old ticket (#4) where this was requested but it was closed as OpenBLAS didn't ship with pkg-config files at the time. This hasn't been true for years...
Dependabot is a bot to create a pull request automatically when the external package is updated, i.e. This will create PR like #76 or #85. https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates I have tested it...
Hello, I am trying to get openblas to work on windows 10. The vcpkg section is fairly well written, but at the end there is a cross compiler section which...
When attempting to compile a crate that depends on `openblas-src` with `static` and `system` features enabled and when using a Windows host, a confusing error message is raised when necessary...
When debugging https://github.com/rust-ndarray/ndarray/issues/1110, I found out that openblas provided by vcpkg is compiled with ilp64. I think the solution to this is to either add ilp64 support to cblas-sys, or...
os: windows 10 professional 19042.1288 vcpkg version: 2021-11-02-af04ebf6274fd6f7a941bff4662b3955c64f6f42 (newest from github) openblas-src version: 0.10 (vcpkg: openblas_x64-windows-static-md) dependencies of project: `ndarray = { version = "0.15.0", features = ["blas"] } blas-src...
These features were supported by the build crate, but not exposed. I picked a default value for NUM_THREADS when USE_THREADS is set, as I see no way to have this...