| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Lea. It is about 2x faster than the old malloc-930716, and behave itself much
better -- it will properly release memory back to the system, and it uses a
combination of brk() for small allocations and mmap() for larger allocations.
-Erik
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
were including libc-lock.h which had a bunch of weak pragmas. Also,
uClibc supplied a number of no-op weak thread functions even though
many weren't needed. This combined result was that sometimes the
functional versions of thread functions in pthread would not override
the weaks in libc.
While fixing this, I also prepended double-underscore to all necessary
weak thread funcs in uClibc, and removed all unused weaks.
I did a test build, but haven't tested this since these changes are
a backport from my working tree. I did test the changes there and
no longer need to explicitly add -lpthread in the perl build for
perl to pass its thread self tests.
|
| | |
|
| | |
|
| |
|
|
|
| |
which was reversed. Provide more consistancy between implementations.
Handle it when people do stupid things like malloc(-1);
|
| |
|
|
| |
want glibc style malloc(0) behavior
|
| | |
|
| |
|
|
| |
-Erik
|
| |
|
|
| |
-Erik
|
| | |
|
| | |
|
| |
|
|
|
| |
spots where I screwed up and forgot to fix realloc to use
free_unlocked() instead of free(). Thanks Ronald!
|
| |
|
|
| |
-Erik
|
| |
|
|
| |
when folks do a malloc(0) using malloc-930716.
|
| |
|
