Hi
Your observation matches my experience. While the compilation using the Accelerate framework works, the subsequent regression test run fails. That is why the OpenBLAS library is still used as the default LAPACK/BLAS instead of the Accelerate framework with Darwin. I have updated the macOS arch files to facilitate the switching between OpenBLAS and the Accelerate framework. Maybe further adjustments are needed to get it working properly.
To the best of my knowledge, there is, however, no evidence yet that the Accelerate framework will provide any significant performance gain compared to OpenBLAS.
Best
Matthias
--
You received this message because you are subscribed to the Google Groups "cp2k" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
cp2k+uns...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/cp2k/e9d370dd-eb2b-409d-9d49-eb1625db925bn%40googlegroups.com.
The CP2K toolchain uses (always) OpenBLAS in a first step to detect the CPU type. The subsequent full build and linking of the OpenBLAS library during the make step, however, is optional, e.g. MKL or other libs providing LAPACK/BLAS can be used instead.
The latest update of the Darwin arch files either links the OpenBLAS library (default) or the Accelerate framework and tries to separate clearly both choices.
To view this discussion visit https://groups.google.com/d/msgid/cp2k/1c9f88e1-34b9-4767-90c0-8a694a03a16bn%40googlegroups.com.