From d0bd3e6f5653a16c8e82c969fb805f4a7d4faf40 Mon Sep 17 00:00:00 2001 From: Jeff Johnston Date: Fri, 11 Jun 2004 20:37:10 +0000 Subject: 2004-06-11 Antony King * libc/include/sys/_types.h: Include and change _flock_t to be of type _LOCK_RECURSIVE_T. * libc/include/sys/reent.h: (_REENT_INIT): Reformat. (_REENT_INIT_PTR): Ditto. Use memset where appropriate. (_global_impure_ptr): New declaration. (_GLOBAL_REENT): Change to be _global_impure_ptr. * libc/include/sys/stdio.h: Include and . (_flockfile)[!_SINGLE_THREAD]: Add code for lock call. (_funlockfile)[!SINGLE_THREAD]: Ditto. * libc/reent/impure.c: Set _global_impure_ptr to _impure_ptr. * libc/stdio/fclose.c: Remove casting of fp lock to _LOCK_RECURSIVE_T. * libc/stdio/findfp.c: Ditto. * libc/stdio/fopen.c: Ditto. * libc/stdio/freopen.c: Ditto. * libc/stdio/vfprintf.c: Ditto. * libc/stdio64/fopen64.c: Ditto. * libc/stdlib/envlock.c: Add default stubs that use generic locking code. * libc/stdlib/mlock.c: Ditto. Jeff Johnston * libc/sys/linux/sys/_types.h (__flock_mutex_t): New subtype. (_flock_t): Change to be a struct containing a single member named mutex which is of type __flock_mutex_t. --- newlib/libc/stdlib/envlock.c | 32 +++++++++++++++++++++----------- 1 file changed, 21 insertions(+), 11 deletions(-) (limited to 'newlib/libc/stdlib/envlock.c') diff --git a/newlib/libc/stdlib/envlock.c b/newlib/libc/stdlib/envlock.c index 8e55de288..24d0083be 100644 --- a/newlib/libc/stdlib/envlock.c +++ b/newlib/libc/stdlib/envlock.c @@ -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 <> 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 <>, or if <> 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 <> 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 <>, or if <> 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 <> may call <<__env_lock>> recursively; that is, the sequence of calls may go <<__env_lock>>, <<__env_lock>>, @@ -36,16 +36,26 @@ that it already holds. */ #include "envlock.h" +#include +#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 } -- cgit v1.2.3