-
Notifications
You must be signed in to change notification settings - Fork 39
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
Segfault when using system-provided lapack #22
Comments
Hey Niklas. In reality, if you're not using any particular optimized version of lapack-blas, linking against the internal copies or the external ones is identical from the performance point of view. Can you please try to test a simple code diagonalizing a trivial matrix? It looks like the error comes from calling eigh(M) with complex M. Let us know. |
Calling eigh(M) works fine. |
Chiming in for a comment: if two different versions of LAPACK (whose implementations should more or less adhere to a standard) behave differently, particularly one of the two segfaults whereas the other gives correct results, I'd say that the problems lies in the failing LAPACK implementation itself. As a matter of fact we have direct control only on the bundled one, which reportedly behaves as intended here, so I'm afraid we could be of very limited help here. You could try switching the minor version of openblas to 0.3.20 (which @SamueleGiuli has been using for a while, without any noticeable issue) or even try switching to MKL or other third-party implementation of LAPACK, if you really need to avoid compiling the version bundled with SciFortran (which I agree, can slowdown quite a bit the installation process). |
Using the lapack version provided by the system (Manjaro 22.0.2 with openblas 0.3.21-1) CDMFT calculations (for various drivers) crash with a segmentation fault during the diagonalization of the impurity Hamiltonian. Compiling SciFortran with -DWITH_BLAS_LAPACK everything works fine.
gdb gives the following backtrace:
log.txt
log_err.txt
The text was updated successfully, but these errors were encountered: