There are well known issues with the gnu openmp variant of openblas in respect to forks of applications. This causes numerous issues especially in the python world where forking is very common. see e.g. https://github.com/xianyi/OpenBLAS/issues/294 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737675
As openblas is integrated into Debians blas alternative system it needs to be rock solid compared to ATLAS and netlib blas. This is known not to be the case for openmp openblas but somewhat working with pthreads. As my viewpoint is very narrow coming from python I want to ask if there are known and ideally reproducable cases where pthread openblas breaks applications but openmp openblas does not? An advantage of the pthread variant is that issues can be fixed in openblas itself while with openmp issues we are at the mercy of the very slow moving gomp. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
