mirror of
git://sourceware.org/git/newlib-cygwin.git
synced 2025-01-15 11:00:04 +08:00
a334e5ef72
* libc/stdlib/envlock.c: changed documented "__env_lock" and
"__env_unlock" prototype from "void *" or "char *" to
"struct _reent *" to match real function. Also added include
of envlock.h.
* libc/stdlib/mlock.c: changed documented "__malloc_lock" and
"__malloc_unlock" prototype from "void *" or "char *" to
"struct _reent *" to match real function.
* libc/stdlib/envlock.h: added "__env_lock" and "__env_unlock"
prototypes (for getenv_r.c and setenv_r.c).
51 lines
1.2 KiB
C
51 lines
1.2 KiB
C
/*
|
|
FUNCTION
|
|
<<__malloc_lock>>, <<__malloc_unlock>>--lock malloc pool
|
|
|
|
INDEX
|
|
__malloc_lock
|
|
INDEX
|
|
__malloc_unlock
|
|
|
|
ANSI_SYNOPSIS
|
|
#include <malloc.h>
|
|
void __malloc_lock (struct _reent *<[reent]>);
|
|
void __malloc_unlock (struct _reent *<[reent]>);
|
|
|
|
TRAD_SYNOPSIS
|
|
void __malloc_lock(<[reent]>)
|
|
struct _reent *<[reent]>;
|
|
|
|
void __malloc_unlock(<[reent]>)
|
|
struct _reent *<[reent]>;
|
|
|
|
DESCRIPTION
|
|
The <<malloc>> family of routines call these functions when they need
|
|
to lock the memory pool. The version of these routines supplied in
|
|
the library does not do anything. If multiple threads of execution
|
|
can call <<malloc>>, or if <<malloc>> 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 <<malloc>> may call <<__malloc_lock>> recursively; that is,
|
|
the sequence of calls may go <<__malloc_lock>>, <<__malloc_lock>>,
|
|
<<__malloc_unlock>>, <<__malloc_unlock>>. Any implementation of these
|
|
routines must be careful to avoid causing a thread to wait for a lock
|
|
that it already holds.
|
|
*/
|
|
|
|
#include <malloc.h>
|
|
|
|
void
|
|
__malloc_lock (ptr)
|
|
struct _reent *ptr;
|
|
{
|
|
}
|
|
|
|
void
|
|
__malloc_unlock (ptr)
|
|
struct _reent *ptr;
|
|
{
|
|
}
|