summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorLines
2012-10-21fix issues with wait constants in stdlib.hRich Felker-6/+5
the W* namespace is not reserved, so the nonstandard ones must be moved under extension features. also WNOHANG and WUNTRACED were missing.
2012-10-21as an extension, have putenv("VAR") behave as unsetenv("VAR")Rich Felker-5/+5
the behavior of putenv is left undefined if the argument does not contain an equal sign, but traditional implementations behave this way and gnulib replaces putenv if it doesn't do this.
2012-10-21accept "nan(n-char-sequence)" in strtod/scanf functionsRich Felker-1/+19
this will prevent gnulib from wrapping our strtod to handle this useless feature.
2012-10-21fix copy/paste error in popen changes that broke signalsRich Felker-1/+1
signal mask was not being restored after fork, but instead blocked again.
2012-10-21complex: make _Complex_I work with gcc -std=c99 -pedantic-errorsnsz-0/+4
2012-10-19support looking up thread-local objects with dlsymRich Felker-0/+6
2012-10-19fix breakage in dlsym for looking up RTLD_DEFAULT, etc.Rich Felker-2/+5
this was broken during the early dynamic-linked TLS commits, which rearranged some of the code for handling new relocation types.
2012-10-19fix struct stat size/padding on microblazeRich Felker-1/+2
2012-10-19fix usage of locks with vforkRich Felker-3/+4
__release_ptc() is only valid in the parent; if it's performed in the child, the lock will be unlocked early then double-unlocked later, corrupting the lock state.
2012-10-19fix crashes in static-linked multithreaded programs without TLSRich Felker-0/+2
2012-10-19fix order of syscall args for microblaze clone syscallRich Felker-3/+2
with this commit, based on testing with patches to qemu which are not yet upstream,
2012-10-18use $CC rather than "$CC" in configure scriptRich Felker-4/+4
this is necessary to allow $CC with arguments in it
2012-10-18inline syscalls for microblazeRich Felker-0/+97
2012-10-18ensure microblaze __set_thread_area returns successRich Felker-1/+2
since it did not set the return-value register, the caller could wrongly interpret this as failure.
2012-10-18better support for reverse-endian variants of arm/mips/microblazeRich Felker-0/+12
these macros are supported by more compilers
2012-10-18avoid raising spurious division-by-zero exception in printfRich Felker-1/+1
2012-10-18floating point environment/exceptions support for mipsRich Felker-3/+73
2012-10-18fix parent-memory-clobber in posix_spawn (environ)Rich Felker-9/+17
2012-10-18overhaul system() and popen() to use vfork; fix various related bugsRich Felker-56/+110
since we target systems without overcommit, special care should be taken that system() and popen(), like posix_spawn(), do not fail in processes whose commit charges are too high to allow ordinary forking. this in turn requires special precautions to ensure that the parent process's signal handlers do not end up running in the shared-memory child, where they could corrupt the state of the parent process. popen has also been updated to use pipe2, so it does not have a fd-leak race in multi-threaded programs. since pipe2 is missing on older kernels, (non-atomic) emulation has been added. some silly bugs in the old code should be gone too.
2012-10-18fix (hopefully; untested) completely broken/incomplete microblaze sigsetjmpRich Felker-3/+12
2012-10-17fix microblaze asm relocations for shared libcRich Felker-6/+6
only @PLT relocations are considered functions for purposes of -Bsymbolic-functions, so always use @PLT. it should not hurt in the static-linked case.
2012-10-17assert() is supposed to have type voidRich Felker-1/+1
2012-10-15add memmem function (gnu extension)Rich Felker-0/+149
based on strstr. passes gnulib tests and a few quick checks of my own.
2012-10-15microblaze TLS relocation support, completely untestedRich Felker-1/+14
2012-10-15add support for TLS variant I, presently needed for arm and mipsRich Felker-17/+79
despite documentation that makes it sound a lot different, the only ABI-constraint difference between TLS variants II and I seems to be that variant II stores the initial TLS segment immediately below the thread pointer (i.e. the thread pointer points to the end of it) and variant I stores the initial TLS segment above the thread pointer, requiring the thread descriptor to be stored below. the actual value stored in the thread pointer register also tends to have per-arch random offsets applied to it for silly micro-optimization purposes. with these changes applied, TLS should be basically working on all supported archs except microblaze. I'm still working on getting the necessary information and a working toolchain that can build TLS binaries for microblaze, but in theory, static-linked programs with TLS and dynamic-linked programs where only the main executable uses TLS should already work on microblaze. alignment constraints have not yet been heavily tested, so it's possible that this code does not always align TLS segments correctly on archs that need TLS variant I.
2012-10-15block uid/gid changes during posix_spawnRich Felker-0/+10
usage of vfork creates a situation where a process of lower privilege may momentarily have write access to the memory of a process of higher privilege. consider the case of a multi-threaded suid program which is calling posix_spawn in one thread while another thread drops the elevated privileges then runs untrusted (relative to the elevated privilege) code as the original invoking user. this untrusted code can then potentially modify the data the child process will use before calling exec, for example changing the pathname or arguments that will be passed to exec. note that if vfork is implemented as fork, the lock will not be held until the child execs, but since memory is not shared it does not matter.
2012-10-14fix overlap of thread stacks with thread tls segmentsRich Felker-2/+1
2012-10-14fix main program TLS alignment for dynamic-linked programsRich Felker-6/+5
this change brings the behavior in line with the static-linked code, which seems to be correct.
2012-10-13workaround broken hidden-visibility handling in pccRich Felker-1/+1
with this change, pcc-built musl libc.so seems to work correctly. the problem is that pcc generates GOT lookups for external-linkage symbols even if they are hidden, rather than using GOT-relative addressing. the entire reason we're using hidden visibility on the __libc object is to make it accessible prior to relocations -- not to mention inexpensive to access. unfortunately, the workaround makes it even more expensive on pcc. when the pcc issue is fixed, an appropriate version test should be added so new pcc can use the much more efficient variant.
2012-10-13ensure pointer decay in inline-asm arg for i386 syscall6Rich Felker-1/+1
this is actually a rather subtle issue: do arrays decay to pointers when used as inline asm args? gcc says yes, but currently pcc says no. hopefully this discrepency in pcc will be fixed, but since the behavior is not clearly defined anywhere I can find, I'm using an explicit operation to cause the decay to occur.
2012-10-13fix namespace clash (libc) in dynlink.cRich Felker-14/+13
this makes it so the #undef libc and __libc name are no longer needed, which were problematic because the "accessor function" mode for accessing the libc struct could not be used, breaking build on any compiler without (working) visibility.
2012-10-13remove dead code from dynamic linkerRich Felker-10/+0
2012-10-11comment possibly-confusing i386 vsyscall asmRich Felker-1/+13
2012-10-11avoid the thread-ptr-init behavior of sigaction when not installing handlerRich Felker-1/+2
this is necessary because posix_spawn calls sigaction after vfork, and if the thread pointer is not already initialized, initializing it in the child corrupts the parent process's state.
2012-10-11i386 vsyscall support (vdso-provided sysenter/syscall instruction based)Rich Felker-82/+69
this doubles the performance of the fastest syscalls on the atom I tested it on; improvement is reportedly much more dramatic on worst-case cpus. cannot be used for cancellable syscalls.
2012-10-08ensure that buffer for decoding auxv at startup is initially zeroRich Felker-1/+1
2012-10-07clean up and refactor program initializationRich Felker-34/+33
the code in __libc_start_main is now responsible for parsing auxv, rather than duplicating the parsing all over the place. this should shave off a few cycles and some code size. __init_libc is left as an external-linkage function despite the fact that it could be static, to prevent it from being inlined and permanently wasting stack space when main is called. a few other minor changes are included, like eliminating per-thread ssp canaries (they were likely broken when combined with certain dlopen usages, and completely unnecessary) and some other unnecessary checks. since this code gets linked into every program, it should be as small and simple as possible.
2012-10-07fix breakage due to initializing thread pointer when loading libsRich Felker-1/+1
at initial program load, all libraries must be loaded before the thread pointer can be setup, since the TP-relative addresses of all initial TLS objects must be constant.
2012-10-06make new TLS setup block even implementation-internals signalsRich Felker-2/+1
this is needed to ensure async-cancel-safety, i.e. to make it safe to access TLS objects when async cancellation is enabled. otherwise, if cancellation were acter upon after the atomic fetch/add but before the thread saved the obtained memory, another access to the same TLS in the cancellation handler could end up performing the atomic fetch/add again, consuming more memory than is actually available and overflowing into other objects on the heap.
2012-10-06don't crash if TLS library is loaded into process with no thread pointerRich Felker-0/+5
2012-10-06fix buggy TLS size/alignment computations in static-linked TLSRich Felker-5/+22
2012-10-06fix symbol acceptance/rejection rules for TLSRich Felker-8/+14
symbol value of 0 is not "undefined" for TLS; it's the address of the first symbol in the TLS segment. however, non-definition TLS references also have values of 0, so check the section. hopefully the new logic is more clear, too.
2012-10-06TLS fixes, mainly alignment handlingRich Felker-39/+48
compute offsets from the thread pointer statically when loading the library, rather than repeating the logic on each thread creation. not only is the latter less efficient at runtime; it also fails to provide solid guarantees that the offsets will remain the same when the initial alignment of memory is different. the new alignment handling is both more rigorous and simpler. the old code was also clobbering TLS bss with random image data in some cases due to using tls_size (size of TLS segment) instead of tls_len (length of the TLS data image).
2012-10-05fix/improve shared library ctor/dtor handling, allow recursive dlopenRich Felker-7/+29
some libraries call dlopen from their constructors, resulting in recursive calls to dlopen. previously, this resulted in deadlock. I'm now unlocking the dlopen lock before running constructors (this is especially important since the lock also blocked pthread_create and was being held while application code runs!) and using a separate recursive mutex protecting the ctor/dtor state instead. in order to prevent the same ctor from being called more than once, a module is considered "constructed" just before the ctor runs. also, switch from using atexit to register each dtor to using a single atexit call to register the dynamic linker's dtor processing as just one handler. this is necessary because atexit performs allocation and may fail, but the library has already been loaded and cannot be backed-out at the time dtor registration is performed. this change also ensures that all dtors run after all atexit functions, rather than in mixed order.
2012-10-05small dynamic linker module search fixRich Felker-1/+2
libraries loaded more than once by pathname should not get shortnames that would cause them to later be used to satisfy non-pathname load requests.
2012-10-05support for TLS in dynamic-loaded (dlopen) modulesRich Felker-47/+115
unlike other implementations, this one reserves memory for new TLS in all pre-existing threads at dlopen-time, and dlopen will fail with no resources consumed and no new libraries loaded if memory is not available. memory is not immediately distributed to running threads; that would be too complex and too costly. instead, assurances are made that threads needing the new TLS can obtain it in an async-signal-safe way from a buffer belonging to the dynamic linker/new module (via atomic fetch-and-add based allocator). I've re-appropriated the lock that was previously used for __synccall (synchronizing set*id() syscalls between threads) as a general pthread_create lock. it's a "backwards" rwlock where the "read" operation is safe atomic modification of the live thread count, which multiple threads can perform at the same time, and the "write" operation is making sure the count does not increase during an operation that depends on it remaining bounded (__synccall or dlopen). in static-linked programs that don't use __synccall, this lock is a no-op and has no cost.
2012-10-05fix race condition in dlopenRich Felker-1/+3
orig_tail was being saved before the lock was obtained, allowing dlopen failure to roll-back other dlopens that had succeeded.
2012-10-05fix incorrect TLS reloc macro names in x86_64 reloc.hRich Felker-3/+3
2012-10-04dynamic-linked TLS support for everything but dlopen'd libsRich Felker-43/+121
currently, only i386 is tested. x86_64 and arm should probably work. the necessary relocation types for mips and microblaze have not been added because I don't understand how they're supposed to work, and I'm not even sure if it's defined yet on microblaze. I may be able to reverse engineer the requirements out of gcc/binutils output.
2012-10-04remove freeing of dynamic linker data when dlopen/dlsym are not usedRich Felker-11/+0
this was an optimization to save/recover a minimal amount of extra memory for use by malloc, that's becoming increasingly costly to keep around. freeing this data: 1. breaks debugging with gdb (it can't find library symbols) 2. breaks thread-local storage in shared libraries it would be possible to disable freeing when TLS is used, but in addition to the above breakages, tracking whether dlopen/dlsym is used adds a cost to every symbol lookup, possibly making program startup slower for large programs. combined with the complexity, it's not worth it. we already save/recover plenty of memory in the dynamic linker with reclaim_gaps.