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

Subversion Repositories or1k

[/] [or1k/] [trunk/] [newlib-1.10.0/] [newlib/] [libc/] [stdlib/] [mlock.c] - Diff between revs 1010 and 1765

Go to most recent revision | Only display areas with differences | Details | Blame | View Log

Rev 1010 Rev 1765
/*
/*
FUNCTION
FUNCTION
<<__malloc_lock>>, <<__malloc_unlock>>--lock malloc pool
<<__malloc_lock>>, <<__malloc_unlock>>--lock malloc pool
 
 
INDEX
INDEX
        __malloc_lock
        __malloc_lock
INDEX
INDEX
        __malloc_unlock
        __malloc_unlock
 
 
ANSI_SYNOPSIS
ANSI_SYNOPSIS
        #include <malloc.h>
        #include <malloc.h>
        void __malloc_lock (struct _reent *<[reent]>);
        void __malloc_lock (struct _reent *<[reent]>);
        void __malloc_unlock (struct _reent *<[reent]>);
        void __malloc_unlock (struct _reent *<[reent]>);
 
 
TRAD_SYNOPSIS
TRAD_SYNOPSIS
        void __malloc_lock(<[reent]>)
        void __malloc_lock(<[reent]>)
        struct _reent *<[reent]>;
        struct _reent *<[reent]>;
 
 
        void __malloc_unlock(<[reent]>)
        void __malloc_unlock(<[reent]>)
        struct _reent *<[reent]>;
        struct _reent *<[reent]>;
 
 
DESCRIPTION
DESCRIPTION
The <<malloc>> family of routines call these functions when they need
The <<malloc>> family of routines call these functions when they need
to lock the memory pool.  The version of these routines supplied in
to lock the memory pool.  The version of these routines supplied in
the library does not do anything.  If multiple threads of execution
the library does not do anything.  If multiple threads of execution
can call <<malloc>>, or if <<malloc>> can be called reentrantly, then
can call <<malloc>>, or if <<malloc>> 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 <<malloc>> may call <<__malloc_lock>> recursively; that is,
A call to <<malloc>> may call <<__malloc_lock>> recursively; that is,
the sequence of calls may go <<__malloc_lock>>, <<__malloc_lock>>,
the sequence of calls may go <<__malloc_lock>>, <<__malloc_lock>>,
<<__malloc_unlock>>, <<__malloc_unlock>>.  Any implementation of these
<<__malloc_unlock>>, <<__malloc_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.
*/
*/
 
 
#include <malloc.h>
#include <malloc.h>
 
 
void
void
__malloc_lock (ptr)
__malloc_lock (ptr)
     struct _reent *ptr;
     struct _reent *ptr;
{
{
}
}
 
 
void
void
__malloc_unlock (ptr)
__malloc_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.