diff options
author | Florian Weimer <fweimer@redhat.com> | 2016-02-19 17:07:45 +0100 |
---|---|---|
committer | Florian Weimer <fweimer@redhat.com> | 2016-02-19 17:07:45 +0100 |
commit | 59eda029a8a35e5f4e5cd7be0f84c6629e48ec6e (patch) | |
tree | 63b915b9258bf371bae30d56f54c5a1eed4b3e61 /sysdeps | |
parent | ca135f824b1dbaf43e4a673de7725db76a51b714 (diff) | |
download | glibc-59eda029a8a35e5f4e5cd7be0f84c6629e48ec6e.zip glibc-59eda029a8a35e5f4e5cd7be0f84c6629e48ec6e.tar.gz glibc-59eda029a8a35e5f4e5cd7be0f84c6629e48ec6e.tar.bz2 |
malloc: Remove NO_THREADS
No functional change. It was not possible to build without
threading support before.
Diffstat (limited to 'sysdeps')
-rw-r--r-- | sysdeps/generic/malloc-machine.h | 19 |
1 files changed, 0 insertions, 19 deletions
diff --git a/sysdeps/generic/malloc-machine.h b/sysdeps/generic/malloc-machine.h index 1ed2d50..71b95c2 100644 --- a/sysdeps/generic/malloc-machine.h +++ b/sysdeps/generic/malloc-machine.h @@ -22,25 +22,6 @@ #include <atomic.h> -#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 |