OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [trunk/] [newlib/] [newlib/] [libc/] [stdlib/] [envlock.c] - Diff between revs 59 and 1765

Only display areas with differences | Details | Blame | View Log

Rev 59 Rev 1765
/*
/*
FUNCTION
FUNCTION
<<__env_lock>>, <<__env_unlock>>--lock environ variable
<<__env_lock>>, <<__env_unlock>>--lock environ variable
 
 
INDEX
INDEX
        __env_lock
        __env_lock
INDEX
INDEX
        __env_unlock
        __env_unlock
 
 
ANSI_SYNOPSIS
ANSI_SYNOPSIS
        #include "envlock.h"
        #include "envlock.h"
        void __env_lock (void *<[reent]>);
        void __env_lock (void *<[reent]>);
        void __env_unlock (void *<[reent]>);
        void __env_unlock (void *<[reent]>);
 
 
TRAD_SYNOPSIS
TRAD_SYNOPSIS
        void __env_lock(<[reent]>)
        void __env_lock(<[reent]>)
        char *<[reent]>;
        char *<[reent]>;
 
 
        void __env_unlock(<[reent]>)
        void __env_unlock(<[reent]>)
        char *<[reent]>;
        char *<[reent]>;
 
 
DESCRIPTION
DESCRIPTION
The <<setenv>> family of routines call these functions when they need
The <<setenv>> family of routines call these functions when they need
to modify the environ variable.  The version of these routines supplied
to modify the environ variable.  The version of these routines supplied
in the library does not do anything.  If multiple threads of execution
in the library does not do anything.  If multiple threads of execution
can call <<setenv>>, or if <<setenv>> can be called reentrantly, then
can call <<setenv>>, or if <<setenv>> can be called reentrantly, then
you need to define your own versions of these functions in order to
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
safely lock the memory pool during a call.  If you do not, the memory
pool may become corrupted.
pool may become corrupted.
 
 
A call to <<setenv>> may call <<__env_lock>> recursively; that is,
A call to <<setenv>> may call <<__env_lock>> recursively; that is,
the sequence of calls may go <<__env_lock>>, <<__env_lock>>,
the sequence of calls may go <<__env_lock>>, <<__env_lock>>,
<<__env_unlock>>, <<__env_unlock>>.  Any implementation of these
<<__env_unlock>>, <<__env_unlock>>.  Any implementation of these
routines must be careful to avoid causing a thread to wait for a lock
routines must be careful to avoid causing a thread to wait for a lock
that it already holds.
that it already holds.
*/
*/
 
 
void
void
__env_lock (ptr)
__env_lock (ptr)
     struct _reent *ptr;
     struct _reent *ptr;
{
{
}
}
 
 
void
void
__env_unlock (ptr)
__env_unlock (ptr)
     struct _reent *ptr;
     struct _reent *ptr;
{
{
}
}
 
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.