In GeneralMatrixMatrix.h, I can see the presence of an OpenMP unnamed critical section. The problem is that it may interfer with user unnamed critical sections, if any. One approach to tackle the problem would be to name the critical section with a somewhat unique identifier (eigen_mat_mul_critical_section or the like). Another (perhaps better) approach would be to use locks from OpenMP. Incidentaly, I don't see the need for an atomic update within a critical section.
hm, actually this critical section could be removed as we are already using an atomic. It seems that it has been introduced by error in the following commit: https://bitbucket.org/eigen/eigen/commits/5a4ca1ad8c53b4a90044ac6c19de9015e53f5f16#LEigen/src/Core/products/GeneralMatrixMatrix.hT141 I've just removed it: https://bitbucket.org/eigen/eigen/commits/7375e4a5b6f8/
-- GitLab Migration Automatic Message -- This bug has been migrated to gitlab.com's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.com/libeigen/eigen/issues/1151.