- 17 3月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 16 3月, 2012 2 次提交
-
-
由 Rich Felker 提交于
a double precision nan, when converted to extended (80-bit) precision, will never end in 0x400, since the corresponding bits do not exist in the original double precision value. thus there's no need to waste time and code size on this check.
-
由 Rich Felker 提交于
-
- 15 3月, 2012 5 次提交
-
-
由 nsz 提交于
long double and float bessel functions are no longer xsi extensions
-
由 nsz 提交于
-
由 Rich Felker 提交于
presumably broken gcc may generate calls to these, and it's said that ffmpeg makes use of sincosf.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
the fsqrt opcode is correctly rounded, but only in the fpu's selected precision mode, which is 80-bit extended precision. to get a correctly rounded double precision output, we check for the only corner cases where two-step rounding could give different results than one-step (extended-precision mantissa ending in 0x400) and adjust the mantissa slightly in the opposite direction of the rounding which the fpu already did (reported in the c1 flag of the fpu status word). this should have near-zero cost in the non-corner cases and at worst very low cost. note that in order for sqrt() to get used when compiling with gcc, the broken, non-conformant builtin sqrt must be disabled.
-
- 14 3月, 2012 5 次提交
-
-
由 Rich Felker 提交于
-
由 nsz 提交于
-
由 nsz 提交于
-
由 nsz 提交于
-
由 Rich Felker 提交于
other cases with %x were probably broken too. I would actually like to go ahead and replace this code in scanf with calls to the new __intparse framework, but for now this calls for a quick and unobtrusive fix without the risk of breaking other things.
-
- 13 3月, 2012 3 次提交
-
-
由 nsz 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
thanks to the hard work of Szabolcs Nagy (nsz), identifying the best (from correctness and license standpoint) implementations from freebsd and openbsd and cleaning them up! musl should now fully support c99 float and long double math functions, and has near-complete complex math support. tgmath should also work (fully on gcc-compatible compilers, and mostly on any c99 compiler). based largely on commit 0376d44a890fea261506f1fc63833e7a686dca19 from nsz's libm git repo, with some additions (dummy versions of a few missing long double complex functions, etc.) by me. various cleanups still need to be made, including re-adding (if they're correct) some asm functions that were dropped.
-
- 03 3月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 02 3月, 2012 6 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
these are mostly untested and adapted directly from corresponding byte string functions and similar.
-
由 Rich Felker 提交于
this is a popular extension some programs depend on, and by using a temporary buffer and strdup rather than malloc prior to the syscall, i've avoided the dependency on free and thus minimized the bloat cost of supporting this feature.
-
- 29 2月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 28 2月, 2012 2 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
this was discussed on the mailing list and no consensus on the preferred solution was reached, so in anticipation of a release, i'm just committing a minimally-invasive solution that avoids the problem by ensuring that multi-threaded-capable programs will always have initialized the thread pointer before any signal handler can run. in the long term we may switch to initializing the thread pointer at program start time whenever the program has the potential to access any per-thread data.
-
- 25 2月, 2012 2 次提交
-
-
由 Rich Felker 提交于
since gcc is failing to generate the necessary ".hidden" directive in the output asm, generate it explicitly with an __asm__ statement...
-
由 Rich Felker 提交于
this was a failed attempt at working around the gcc 3 visibility bug affecting x86_64. subsequent patch will address it with an ugly but working hack.
-
- 24 2月, 2012 3 次提交
-
-
由 Rich Felker 提交于
in gcc 3, the visibility attribute must be placed on both the declaration and on the definition. if it's omitted from the definition, the compiler fails to emit the ".hidden" directive in the assembly, and the linker will either generate textrels (if supported, such as on i386) or refuse to link (on targets where certain types of textrels are forbidden or impossible without further assumptions about memory layout, such as on x86_64). this patch also unifies the decision about when to use visibility into libc.h and makes the visibility in the utf-8 state machine tables based on libc.h rather than a duplicate test.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
uninitialized file descriptor was being closed on return, causing stdin to be closed in many cases.
-
- 18 2月, 2012 2 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
- 11 2月, 2012 2 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
- 10 2月, 2012 1 次提交
-
-
由 Rich Felker 提交于
even if pthread_create/exit code is not linked, run flag needs to be checked and cleanup function potentially run on pop. thus, move the code to the module that's always linked when pthread_cleanup_push/pop is used.
-
- 09 2月, 2012 3 次提交
-
-
由 Rich Felker 提交于
the old abi was intended to duplicate glibc's abi at the expense of being ugly and slow, but it turns out glib was not even using that abi except on non-gcc-compatible compilers (which it doesn't even support) and was instead using an exceptions-in-c/unwind-based approach whose abi we could not duplicate anyway without nasty dwarf2/unwind integration. the new abi is copied from a very old glibc abi, which seems to still be supported/present in current glibc. it avoids all unwinding, whether by sjlj or exceptions, and merely maintains a linked list of cleanup functions to be called from the context of pthread_exit. i've made some care to ensure that longjmp out of a cleanup function should work, even though it is not required to. this change breaks abi compatibility with programs which were using pthread cancellation, which is unfortunate, but that's why i'm making the change now rather than later. considering that most pthread features have not been usable until recently anyway, i don't see it as a major issue at this point.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
- 08 2月, 2012 1 次提交
-
-
由 Rich Felker 提交于
i'm not sure that it's "correct" for dlopen to block cancellation when calling constructors for libraries it loads, but it sure seems like the right thing. in any case, dlopen itself needs cancellation blocked.
-