On sage-on-gentoo on a Debian prefix my friend Steve Trogdon noticed some random failures that seemed related to the use of openmp in m4ri. Disabling openmp solved made the issue go away.
After he investigated further it seems that the L3 cache of the machine is misdetected. Entering some safe values again made it go away.
See cschwan/sage-on-gentoo#475 for the full discussion. I am wondering if the L3 cache detection routine needs updating for newer cpus. The macro hasn't received an update in years (not only in m4ri but upstream as well).
On sage-on-gentoo on a Debian prefix my friend Steve Trogdon noticed some random failures that seemed related to the use of openmp in m4ri. Disabling openmp solved made the issue go away.
After he investigated further it seems that the L3 cache of the machine is misdetected. Entering some safe values again made it go away.
See cschwan/sage-on-gentoo#475 for the full discussion. I am wondering if the L3 cache detection routine needs updating for newer cpus. The macro hasn't received an update in years (not only in m4ri but upstream as well).