From 59eda029a8a35e5f4e5cd7be0f84c6629e48ec6e Mon Sep 17 00:00:00 2001 From: Florian Weimer Date: Fri, 19 Feb 2016 17:07:45 +0100 Subject: malloc: Remove NO_THREADS No functional change. It was not possible to build without threading support before. --- sysdeps/generic/malloc-machine.h | 19 ------------------- 1 file changed, 19 deletions(-) (limited to 'sysdeps/generic/malloc-machine.h') diff --git a/sysdeps/generic/malloc-machine.h b/sysdeps/generic/malloc-machine.h index 1ed2d50a20..71b95c23e9 100644 --- a/sysdeps/generic/malloc-machine.h +++ b/sysdeps/generic/malloc-machine.h @@ -22,25 +22,6 @@ #include -#ifndef mutex_init /* No threads, provide dummy macros */ - -# define NO_THREADS - -/* The mutex functions used to do absolutely nothing, i.e. lock, - trylock and unlock would always just return 0. However, even - without any concurrently active threads, a mutex can be used - legitimately as an `in use' flag. To make the code that is - protected by a mutex async-signal safe, these macros would have to - be based on atomic test-and-set operations, for example. */ -typedef int mutex_t; - -# define mutex_init(m) (*(m) = 0) -# define mutex_lock(m) ({ *(m) = 1; 0; }) -# define mutex_trylock(m) (*(m) ? 1 : ((*(m) = 1), 0)) -# define mutex_unlock(m) (*(m) = 0) - -#endif /* !defined mutex_init */ - #ifndef atomic_full_barrier # define atomic_full_barrier() __asm ("" ::: "memory") #endif -- cgit 1.4.1