You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've hit a nearly identical bug on an Intel windows ICC/VS2015 system calling the Intel LAPACK implementation.
This may be the result of LAPACK/BLAS interfaces being defined by legacy Fortran ABIs, which are not specified and not natively compliant with C++. Trilinos attempts to the detect fortran's mangling scheme and ABI based on the current fortran compiler, which may not match the ABI used for the library. This for example is why by default Teuchos's sdot will crash with Apple's veclib: the VecLib-defined ABI uses a different fortran calling convention.
The best solution may be to try to use the cblas and lapacke. The VecLib framework, the OpenBLAS library, and the install the correct C interface headers for their routines so they could be used without having to rely on potentially fragile ABI detection.
The text was updated successfully, but these errors were encountered:
Not sure what's happening here, but after upgrading to catalina and GCC10 I'm getting crashes inside the Anasazi Davidson solver due to a lapack call:
where the offending LAPACK call is:
and
xc=1
.I am unable to reproduce this in a standalone C++ test that calls the same lapack function with the same trilinos install :(
Environment
macOS Catalina with
apple-clang@12.0.0
usinggcc@10.2.0
for gfortran support:Possible
I've hit a nearly identical bug on an Intel windows ICC/VS2015 system calling the Intel LAPACK implementation.
This may be the result of LAPACK/BLAS interfaces being defined by legacy Fortran ABIs, which are not specified and not natively compliant with C++. Trilinos attempts to the detect fortran's mangling scheme and ABI based on the current fortran compiler, which may not match the ABI used for the library. This for example is why by default Teuchos's
sdot
will crash with Apple's veclib: the VecLib-defined ABI uses a different fortran calling convention.The best solution may be to try to use the
cblas
andlapacke
. The VecLib framework, the OpenBLAS library, and the install the correct C interface headers for their routines so they could be used without having to rely on potentially fragile ABI detection.The text was updated successfully, but these errors were encountered: