Use libc from agbcc instead of standalone newlib\nYou must have AGBCC commit 80d029caec189587f8b9294b6c8a5a489b8f5f88 in order to compile pmd_red.gbalibc

1 files changed, 0 insertions, 50 deletions

diff --git a/newlib/libc/stdlib/mlock.c b/newlib/libc/stdlib/mlock.c
deleted file mode 100644
index e7f7242..0000000
--- a/newlib/libc/stdlib/mlock.c
+++ /dev/null
@@ -1,50 +0,0 @@
-/*
-FUNCTION
-<<__malloc_lock>>, <<__malloc_unlock>>--lock malloc pool
-
-INDEX
-	__malloc_lock
-INDEX
-	__malloc_unlock
-
-ANSI_SYNOPSIS
-	#include <malloc.h>
-	void __malloc_lock (void *<[reent]>);
-	void __malloc_unlock (void *<[reent]>);
-
-TRAD_SYNOPSIS
-	void __malloc_lock(<[reent]>)
-	char *<[reent]>;
-
-	void __malloc_unlock(<[reent]>)
-	char *<[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;
-{
-}