From e25626677f8076eb3ce94586136c5464ee154381 Mon Sep 17 00:00:00 2001 From: Thomas Munro Date: Tue, 30 Jul 2024 21:45:01 +1200 Subject: Remove --disable-spinlocks. A later change will require atomic support, so it wouldn't make sense for a hypothetical new system not to be able to implement spinlocks. Reviewed-by: Heikki Linnakangas Reviewed-by: Tom Lane (concept, not the patch) Reviewed-by: Andres Freund (concept, not the patch) Discussion: https://postgr.es/m/3351991.1697728588%40sss.pgh.pa.us --- configure.ac | 13 ------------- 1 file changed, 13 deletions(-) (limited to 'configure.ac') diff --git a/configure.ac b/configure.ac index 0089e78b687..a72169f5745 100644 --- a/configure.ac +++ b/configure.ac @@ -186,12 +186,6 @@ PGAC_ARG_BOOL(enable, rpath, yes, [do not embed shared library search path in executables]) AC_SUBST(enable_rpath) -# -# Spinlocks -# -PGAC_ARG_BOOL(enable, spinlocks, yes, - [do not use spinlocks]) - # # Atomic operations # @@ -1296,13 +1290,6 @@ failure. It is possible the compiler isn't looking in the proper directory. Use --without-zlib to disable zlib support.])]) fi -if test "$enable_spinlocks" = yes; then - AC_DEFINE(HAVE_SPINLOCKS, 1, [Define to 1 if you have spinlocks.]) -else - AC_MSG_WARN([ -*** Not using spinlocks will cause poor performance.]) -fi - if test "$enable_atomics" = yes; then AC_DEFINE(HAVE_ATOMICS, 1, [Define to 1 if you want to use atomics if available.]) else -- cgit v1.2.3