Force no lazy-lock on Windows.

Monitoring thread creation is unimplemented for Windows, which means
lazy-lock cannot function correctly.

This resolves #310.
This commit is contained in:
Jason Evans 2016-11-02 08:54:07 -07:00
parent 7b0a8b74f0
commit eee1ca655e

View File

@ -1404,9 +1404,17 @@ fi
], ],
[enable_lazy_lock=""] [enable_lazy_lock=""]
) )
if test "x$enable_lazy_lock" = "x" -a "x${force_lazy_lock}" = "x1" ; then if test "x${enable_lazy_lock}" = "x" ; then
AC_MSG_RESULT([Forcing lazy-lock to avoid allocator/threading bootstrap issues]) if test "x${force_lazy_lock}" = "x1" ; then
enable_lazy_lock="1" AC_MSG_RESULT([Forcing lazy-lock to avoid allocator/threading bootstrap issues])
enable_lazy_lock="1"
else
enable_lazy_lock="0"
fi
fi
if test "x${enable_lazy_lock}" = "x1" -a "x${abi}" = "xpecoff" ; then
AC_MSG_RESULT([Forcing no lazy-lock because thread creation monitoring is unimplemented])
enable_lazy_lock="0"
fi fi
if test "x$enable_lazy_lock" = "x1" ; then if test "x$enable_lazy_lock" = "x1" ; then
if test "x$abi" != "xpecoff" ; then if test "x$abi" != "xpecoff" ; then
@ -1417,8 +1425,6 @@ if test "x$enable_lazy_lock" = "x1" ; then
]) ])
fi fi
AC_DEFINE([JEMALLOC_LAZY_LOCK], [ ]) AC_DEFINE([JEMALLOC_LAZY_LOCK], [ ])
else
enable_lazy_lock="0"
fi fi
AC_SUBST([enable_lazy_lock]) AC_SUBST([enable_lazy_lock])