Welcome to mirror list, hosted at ThFree Co, Russian Federation.

cygwin.com/git/newlib-cygwin.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'newlib/libc/stdlib/envlock.c')
-rw-r--r--newlib/libc/stdlib/envlock.c34
1 files changed, 12 insertions, 22 deletions
diff --git a/newlib/libc/stdlib/envlock.c b/newlib/libc/stdlib/envlock.c
index 74c85a8f5..8e55de288 100644
--- a/newlib/libc/stdlib/envlock.c
+++ b/newlib/libc/stdlib/envlock.c
@@ -1,6 +1,6 @@
/*
FUNCTION
-<<__env_lock>>, <<__env_unlock>>---lock environ variable
+<<__env_lock>>, <<__env_unlock>>--lock environ variable
INDEX
__env_lock
@@ -9,24 +9,24 @@ INDEX
ANSI_SYNOPSIS
#include "envlock.h"
- void __env_lock (struct _reent *<[reent]>);
- void __env_unlock (struct _reent *<[reent]>);
+ void __env_lock (struct _reent *<[reent]>);
+ void __env_unlock (struct _reent *<[reent]>);
TRAD_SYNOPSIS
void __env_lock(<[reent]>)
- struct _reent *<[reent]>;
+ struct _reent *<[reent]>;
void __env_unlock(<[reent]>)
- struct _reent *<[reent]>;
+ struct _reent *<[reent]>;
DESCRIPTION
-The <<setenv>> family of routines call these functions when they need to
-modify the environ variable. The version of these routines supplied in the
-library use the lock API defined in sys/lock.h. If multiple threads of
-execution can call <<setenv>>, or if <<setenv>> can be called reentrantly,
-then you need to define your own versions of these functions in order to
-safely lock the memory pool during a call. If you do not, the memory pool
-may become corrupted.
+The <<setenv>> family of routines call these functions when they need
+to modify the environ variable. The version of these routines supplied
+in the library does not do anything. If multiple threads of execution
+can call <<setenv>>, or if <<setenv>> can be called reentrantly, then
+you need to define your own versions of these functions in order to
+safely lock the memory pool during a call. If you do not, the memory
+pool may become corrupted.
A call to <<setenv>> may call <<__env_lock>> recursively; that is,
the sequence of calls may go <<__env_lock>>, <<__env_lock>>,
@@ -36,26 +36,16 @@ that it already holds.
*/
#include "envlock.h"
-#include <sys/lock.h>
-#ifndef __SINGLE_THREAD__
-__LOCK_INIT_RECURSIVE(static, __env_lock_object);
-#endif
void
__env_lock (ptr)
struct _reent *ptr;
{
-#ifndef __SINGLE_THREAD__
- __lock_acquire_recursive (__env_lock_object);
-#endif
}
void
__env_unlock (ptr)
struct _reent *ptr;
{
-#ifndef __SINGLE_THREAD__
- __lock_release_recursive (__env_lock_object);
-#endif
}