| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | make thread-pointer-loading asm non-volatile | Rich Felker | 2018-10-16 | 1 | -1/+1 |
| | | | | | | | | | | | this will allow the compiler to cache and reuse the result, meaning we no longer have to take care not to load it more than once for the sake of archs where the load may be expensive. depends on commit 1c84c99913bf1cd47b866ed31e665848a0da84a2 for correctness, since otherwise the compiler could hoist loads during stage 3 of dynamic linking before the initial thread-pointer setup. | ||||
| * | fix crashes in x32 __tls_get_addr | rofl0r | 2017-01-13 | 1 | -0/+2 |
| | | | | | | | x32 has another gratuitous difference to all other archs: it passes an array of 64bit values to __tls_get_addr(). usually it is an array of size_t. | ||||
| * | properly access mcontext_t program counter in cancellation handler | Rich Felker | 2015-11-02 | 1 | -1/+1 |
| | | | | | | | | | | using the actual mcontext_t definition rather than an overlaid pointer array both improves correctness/readability and eliminates some ugly hacks for archs with 64-bit registers bit 32-bit program counter. also fix UB due to comparison of pointers not in a common array object. | ||||
| * | fix stack protector crashes on x32 & powerpc due to misplaced TLS canary | Rich Felker | 2015-05-06 | 1 | -0/+2 |
| | | | | | | | | | | | | | | | | | | | | i386, x86_64, x32, and powerpc all use TLS for stack protector canary values in the default stack protector ABI, but the location only matched the ABI on i386 and x86_64. on x32, the expected location for the canary contained the tid, thus producing spurious mismatches (resulting in process termination) upon fork. on powerpc, the expected location contained the stdio_locks list head, so returning from a function after calling flockfile produced spurious mismatches. in both cases, the random canary was not present, and a predictable value was used instead, making the stack protector hardening much less effective than it should be. in the current fix, the thread structure has been expanded to have canary fields at all three possible locations, and archs that use a non-default location must define a macro in pthread_arch.h to choose which location is used. for most archs (which lack TLS canary ABI) the choice does not matter. | ||||
| * | fix broken cancellation on x32 due to incorrect saved-PC offset | Rich Felker | 2015-05-02 | 1 | -1/+1 |
| | | |||||
| * | import vanilla x86_64 code as x32 | rofl0r | 2014-02-23 | 1 | -0/+10 |
 |
index : mirror/musl | |
| mirror of git://git.musl-libc.org/musl | Leah Neukirchen |
| about summary refs log tree commit diff |