src-test2/lib/libc/stdlib/malloc.c, branch release/4.0.0_cvs

This commit was manufactured by cvs2svn to create tag

2000-03-20T08:47:53Z

'RELENG_4_0_0_RELEASE'. This commit was manufactured to restore the state of the 4.0-RELEASE image. Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

Simplify sytem call renaming. Instead of _foo() <-- _libc_foo <-- foo(),

2000-01-27T23:07:25Z

just use _foo() <-- foo(). In the case of a libpthread that doesn't do call conversion (such as linuxthreads and our upcoming libpthread), this is adequate. In the case of libc_r, we still need three names, which are now _thread_sys_foo() <-- _foo() <-- foo(). Convert all internal libc usage of: aio_suspend(), close(), fsync(), msync(), nanosleep(), open(), fcntl(), read(), and write() to _foo() instead of foo(). Remove all internal libc usage of: creat(), pause(), sleep(), system(), tcdrain(), wait(), and waitpid(). Make thread cancellation fully POSIX-compliant. Suggested by: deischen

Add three-tier symbol naming in support of POSIX thread cancellation

2000-01-12T09:23:48Z

points. For library functions, the pattern is __sleep() <-- _libc_sleep() <-- sleep(). The arrows represent weak aliases. For system calls, the pattern is _read() <-- _libc_read() <-- read().

$Id$ -> $FreeBSD$

1999-08-28T00:22:10Z

Back out previous commit after discussing it with Dmitrij Tejblum.

1999-07-07T21:01:20Z

Always set errno to ENOMEM when returning 0 from malloc() or realloc().

1999-07-07T19:54:08Z

Approved by: phk

Disable the "Hint" option in phkmalloc as default. Recent VM system

1999-03-28T14:16:05Z

changes have made this too expensive. This gains about 1.25% on worldstone on my SMP machine. Swap-less machines, for instance PicoBSDs, and machines which experience page-out trafic, check with top(1), will probably want to reenable this with: ln -s H /etc/malloc.conf Suggested by: alc (&dyson ?)

Delete the XXX comments that refer to spinlock recursion. The malloc/free/

1998-09-30T06:13:59Z

realloc functions check for recursion within the malloc code itself. In a thread-safe library, the single spinlock ensures that no two threads go inside the protected code at the same time. The thread implementation is responsible for ensuring that the spinlock does in fact protect malloc. There was a window of opportunity in which this was not the case. I'll fix that with a commit RSN.

Use 8k pagesize on alpha, not 4k.

1998-09-23T21:26:04Z

Back out part of previous commit (even though it's technically correct).

1998-09-20T01:07:50Z

Our spinlock implementation allows a particular thread to obtain a lock multiple times, but release the lock with a single unlock call. Since we're detecting recursion, we know the lock is already owned by the current thread in a previous call and must not be released in the current call. This is really far too dependent on this particular spinlock implementation, so I've added commented out calls to THREAD_UNLOCK in the appropriate places. We can activate this code when spinlock is taught to count each lock operation.