about summary refs log tree commit diff
Commit message (Collapse)AuthorAgeFilesLines
* update release notes v0.7.5Rich Felker2011-04-011-1/+2
|
* avoid over-allocation of brk on first mallocRich Felker2011-04-011-4/+4
| | | | | | | if init_malloc returns positive (successful first init), malloc will retry getting a chunk from the free bins rather than expanding the heap again. also pass init_malloc a hint for the size of the initial allocation.
* reorganize the __libc structure for threaded performance issuesRich Felker2011-04-011-6/+6
| | | | | | | we want to keep atomically updated fields (locks and thread count) and really anything writable far away from frequently-needed function pointers. stuff some rarely-needed function pointers in between to pad, hopefully up to a cache line boundary.
* simplify setting result on thread cancellationRich Felker2011-04-011-1/+1
|
* use bss instead of mmap for main thread's pthread thread-specific dataRich Felker2011-04-012-9/+4
| | | | this simplifies code and removes a failure case
* remove obsolete and useless useconds_t typeRich Felker2011-04-015-7/+4
|
* somehow timespec tv_nsec had the wrong type on x86_64... fixedRich Felker2011-04-011-1/+1
|
* fix misspelled PTHREAD_CANCELED constantRich Felker2011-04-012-2/+2
|
* document more changesRich Felker2011-04-011-0/+6
|
* document changes for upcoming 0.7.5 releaseRich Felker2011-04-011-0/+19
|
* use a_store to set cancel flag in pthread_cancel, to ensure a barrierRich Felker2011-04-011-1/+1
|
* simplify pthread_key_deleteRich Felker2011-03-311-1/+1
| | | | | calling this function on an uninitialized key value is UB, so there is no need to check that the table pointer was initialized.
* greatly simplify pthread_key_create (~20% size reduction)Rich Felker2011-03-311-10/+9
|
* add some missing prototypes for nonstandard functions (strsep, clearenv)Rich Felker2011-03-302-0/+2
|
* avoid all malloc/free in timer creation/destructionRich Felker2011-03-307-31/+22
| | | | | | | | | | instead of allocating a userspace structure for signal-based timers, simply use the kernel timer id. we use the fact that thread pointers will always be zero in the low bit (actually more) to encode integer timerid values as pointers. also, this change ensures that the timer_destroy syscall has completed before the library timer_destroy function returns, in case it matters.
* optimize timer creation and possibly protect against some minor racesRich Felker2011-03-302-16/+19
| | | | | | | | | the major idea of this patch is not to depend on having the timer pointer delivered to the signal handler, and instead use the thread pointer to get the callback function address and argument. this way, the parent thread can make the timer_create syscall while the child thread is starting, and it should never have to block waiting for the barrier.
* avoid crash on stupid but allowable usage of pthread_mutex_unlockRich Felker2011-03-301-1/+3
| | | | | | | unlocking an unlocked mutex is not UB for robust or error-checking mutexes, so we must avoid calling __pthread_self (which might crash due to lack of thread-register initialization) until after checking that the mutex is locked.
* rename __simple_malloc.c to lite_malloc.c - yes this affects behavior!Rich Felker2011-03-301-0/+0
| | | | | | | | | | | | | | | why does this affect behavior? well, the linker seems to traverse archive files starting from its current position when resolving symbols. since calloc.c comes alphabetically (and thus in sequence in the archive file) between __simple_malloc.c and malloc.c, attempts to resolve the "malloc" symbol for use by calloc.c were pulling in the full malloc.c implementation rather than the __simple_malloc.c implementation. as of now, lite_malloc.c and malloc.c are adjacent in the archive and in the correct order, so malloc.c should never be used to resolve "malloc" unless it's already needed to resolve another symbol ("free" or "realloc").
* streamline mutex unlock to remove a useless branch, use a_store to unlockRich Felker2011-03-301-2/+6
| | | | | | | | | this roughly halves the cost of pthread_mutex_unlock, at least for non-robust, normal-type mutexes. the a_store change is in preparation for future support of archs which require a memory barrier or special atomic store operation, and also should prevent the possibility of the compiler misordering writes.
* cheap special-case optimization for normal mutexesRich Felker2011-03-301-0/+4
| | | | | | | cycle-level benchmark on atom cpu showed typical pthread_mutex_lock call dropping from ~120 cycles to ~90 cycles with this change. benefit may vary with compiler options and version, but this optimization is very cheap to make and should always help some.
* reorder timer initialization so that timer_create does not depend on freeRich Felker2011-03-292-9/+17
| | | | | this allows small programs which only create times, but never delete them, to use simple_malloc instead of the full malloc.
* missing prototype for wcscoll (stub)Rich Felker2011-03-291-0/+1
|
* revert mutex "optimization" that turned out to be worseRich Felker2011-03-291-1/+1
|
* implement POSIX timersRich Felker2011-03-297-6/+160
| | | | | | | | this implementation is superior to the glibc/nptl implementation, in that it gives true realtime behavior. there is no risk of timer expiration events being lost due to failed thread creation or failed malloc, because the thread is created as time creation time, and reused until the timer is deleted.
* major improvements to cancellation handlingRich Felker2011-03-294-8/+19
| | | | | | | | | | | | | - there is no longer any risk of spoofing cancellation requests, since the cancel flag is set in pthread_cancel rather than in the signal handler. - cancellation signal is no longer unblocked when running the cancellation handlers. instead, pthread_create will cause any new threads created from a cancellation handler to unblock their own cancellation signal. - various tweaks in preparation for POSIX timer support.
* some preliminaries for adding POSIX timersRich Felker2011-03-293-2/+6
|
* fix tempnam name generation, and a small bug in tmpnam on retry limitRich Felker2011-03-292-21/+20
|
* make tmpfile fail after exceeding max tries.Rich Felker2011-03-291-2/+6
|
* fix tmpnam to generate better names, not depend on non-ISO-C symbolsRich Felker2011-03-291-25/+17
|
* fix messed-up errno if remove fails for a non-EISDIR reasonRich Felker2011-03-291-2/+2
|
* learned something new - remove is supposed to support directories on POSIXRich Felker2011-03-291-1/+3
|
* revert some more spin optimizations that turned out to be pessimizationsRich Felker2011-03-283-4/+3
|
* fix bug from syscall overhaul: extra __syscall_ret call for 0-arg syscallsRich Felker2011-03-281-1/+1
| | | | | this mainly just caused bloat, but could corrupt errno if a 0-arg syscall ever failed.
* fix broken spinlock due to miscompilationRich Felker2011-03-281-1/+1
| | | | actually this trick also seems to have made the uncontended case slower.
* prototype for getpassRich Felker2011-03-281-0/+4
|
* remove useless field in pthread struct (wasted a good bit of space)Rich Felker2011-03-281-1/+0
|
* fix getc - the classic error of trying to store EOF+0-255 in a char type..Rich Felker2011-03-281-3/+3
|
* major stdio overhaul, using readv/writev, plus other changesRich Felker2011-03-2837-281/+258
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the biggest change in this commit is that stdio now uses readv to fill the caller's buffer and the FILE buffer with a single syscall, and likewise writev to flush the FILE buffer and write out the caller's buffer in a single syscall. making this change required fundamental architectural changes to stdio, so i also made a number of other improvements in the process: - the implementation no longer assumes that further io will fail following errors, and no longer blocks io when the error flag is set (though the latter could easily be changed back if desired) - unbuffered mode is no longer implemented as a one-byte buffer. as a consequence, scanf unreading has to use ungetc, to the unget buffer has been enlarged to hold at least 2 wide characters. - the FILE structure has been rearranged to maintain the locations of the fields that might be used in glibc getc/putc type macros, while shrinking the structure to save some space. - error cases for fflush, fseek, etc. should be more correct. - library-internal macros are used for getc_unlocked and putc_unlocked now, eliminating some ugly code duplication. __uflow and __overflow are no longer used anywhere but these macros. switch to read or write mode is also separated so the code can be better shared, e.g. with ungetc. - lots of other small things.
* match glibc/lsb cancellation abi on i386Rich Felker2011-03-258-0/+57
| | | | | | | | glibc made the ridiculous choice to use pass-by-register calling convention for these functions, which is impossible to duplicate directly on non-gcc compilers. instead, we use ugly asm to wrap and convert the calling convention. presumably this works with every compiler anyone could potentially want to use.
* remove -Wno-pointer-sign example from dist/config.makRich Felker2011-03-251-1/+0
|
* fix all implicit conversion between signed/unsigned pointersRich Felker2011-03-2519-48/+44
| | | | | | | sadly the C language does not specify any such implicit conversion, so this is not a matter of just fixing warnings (as gcc treats it) but actual errors. i would like to revisit a number of these changes and possibly revise the types used to reduce the number of casts required.
* simplify and optimize FILE lock handlingRich Felker2011-03-245-14/+14
|
* prepare pthread_spin_unlock for archs that need memory barriersRich Felker2011-03-241-1/+2
|
* optimize contended case for pthread_spin_trylockRich Felker2011-03-241-1/+2
|
* optimize spinlock spinRich Felker2011-03-241-1/+1
|
* fix non-atomicity of putsRich Felker2011-03-241-1/+5
|
* overhaul cancellation to fix resource leaks and dangerous behavior with signalsRich Felker2011-03-2414-13/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | this commit addresses two issues: 1. a race condition, whereby a cancellation request occurring after a syscall returned from kernelspace but before the subsequent CANCELPT_END would cause cancellable resource-allocating syscalls (like open) to leak resources. 2. signal handlers invoked while the thread was blocked at a cancellation point behaved as if asynchronous cancellation mode wer in effect, resulting in potentially dangerous state corruption if a cancellation request occurs. the glibc/nptl implementation of threads shares both of these issues. with this commit, both are fixed. however, cancellation points encountered in a signal handler will not be acted upon if the signal was received while the thread was already at a cancellation point. they will of course be acted upon after the signal handler returns, so in real-world usage where signal handlers quickly return, it should not be a problem. it's possible to solve this problem too by having sigaction() wrap all signal handlers with a function that uses a pthread_cleanup handler to catch cancellation, patch up the saved context, and return into the cancellable function that will catch and act upon the cancellation. however that would be a lot of complexity for minimal if any benefit...
* very cheap double-free checks in mallocRich Felker2011-03-231-0/+4
|
* global cleanup to use the new syscall interfaceRich Felker2011-03-20160-238/+180
|
* if returning errno value directly from a syscall, we need to negate it.Rich Felker2011-03-193-3/+3
|