- 12 12月, 2012 4 次提交
-
-
由 Szabolcs Nagy 提交于
modifications: * avoid unsigned->signed conversions * removed various volatile hacks * use FORCE_EVAL when evaluating only for side-effects * factor out R() rational approximation instead of manual inline * __invtrigl.h now only provides __invtrigl_R, __pio2_hi and __pio2_lo * use 2*pio2_hi, 2*pio2_lo instead of pi_hi, pi_lo otherwise the logic is not changed, long double versions will need a revisit when a genaral long double cleanup happens
-
由 Szabolcs Nagy 提交于
modifications: * avoid unsigned->signed integer conversion * do not handle special cases when they work correctly anyway * more strict threshold values (0x1p26 instead of 0x1p28 etc) * smaller code, cleaner branching logic * same precision as the old code: acosh(x) has up to 2ulp error in [1,1.125] asinh(x) has up to 1.6ulp error in [0.125,0.5], [-0.5,-0.125] atanh(x) has up to 1.7ulp error in [0.125,0.5], [-0.5,-0.125]
-
由 Szabolcs Nagy 提交于
j0l,j1l,jnl,y0l,j1l,jnl are gnu extensions, bsd and posix do not have them. noone seems to use them and there is no plan to implement them any time soon so we shouldn't declare them in math.h.
-
由 Szabolcs Nagy 提交于
-
- 11 12月, 2012 4 次提交
-
-
由 Rich Felker 提交于
this bug seems to have caused any failure by pipe2 on such systems to set errno to 1, rather than the proper error code.
-
由 Rich Felker 提交于
despite glibc using __key and __seq rather than key and seq, some applications, notably busybox, assume the names are key and seq unless glibc is being used. and the names key and seq are really the ones that _should_ be exposed when not attempting to present a standards-conforming namespace; apps should not be using names that begin with double-underscore. thus, the optimal fix is to use key and seq as the actual names of the members when in bsd/gnu source profile, and define macros for __key and __seq that redirect to plain key and seq.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
traditionally, both BSD and GNU systems have it this way. sys/syscall.h is purely syscall number macros. presently glibc exposes the syscall declaration in unistd.h only with _GNU_SOURCE, but that does not reflect historical practice.
-
- 08 12月, 2012 5 次提交
-
-
由 Rich Felker 提交于
a while back, gcc switched from using the old _init/_fini fragments method for calling ctors and dtors on arm to the __init_array and __fini_array method. unfortunately, on glibc this depends on ugly hacks involving making libc.so a linker script and pulling parts of libc into the main program binary. so I cheat a little bit, and just write asm to iterate over the init/fini arrays from the _init/_fini asm. the same approach could be used on any arch it's needed on, but for now arm is the only one.
-
由 Rich Felker 提交于
this change fixes an obscure issue with some nonstandard kernels, where the initial brk syscall returns a pointer just past the end of bss rather than the beginning of a new page. in that case, the dynamic linker has already reclaimed the space between the end of bss and the page end for use by malloc, and memory corruption (allocating the same memory twice) will occur when malloc again claims it on the first call to brk.
-
由 Rich Felker 提交于
if there's evidence of any use for it, we can add it back later. as far as I can tell, glibc has it only for internal use (and musl uses a direct syscall in that case rather than a function call), not for exposing it to applications.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
- 07 12月, 2012 18 次提交
-
-
由 Rich Felker 提交于
in case of mmap-obtained chunks, end points past the end of the mapping and reading it may fault. since the value is not needed until after the conditional, move the access to prevent invalid reads.
-
由 Rich Felker 提交于
they were accidentally exposed under just baseline POSIX, which is a big namespace pollution issue. thankfully glibc only exposes them under _GNU_SOURCE, not under any of its other options, so omitting the pollution in the default _BSD_SOURCE profile does not hurt application compatibility at all.
-
由 Rich Felker 提交于
previously the names were exposed as key/seq with _GNU_SOURCE and __ipc_perm_key/__ipc_perm/seq otherwise, whereas glibc always uses __key and __seq for the names. thus, the old behavior never matched glibc, and the new behavior always does, regardless of feature test macros. for now, i'm leaving the renaming here in sys/ipc.h where it's easy to change globally for all archs, in case something turns out to be wrong, but eventually the names could just be incorporated directly into the bits headers for each arch and the renaming removed.
-
由 rofl0r 提交于
-
由 rofl0r 提交于
-
由 rofl0r 提交于
that way it's consistent with existing sig* functions, and saves some code size.
-
由 rofl0r 提交于
-
由 rofl0r 提交于
-
由 rofl0r 提交于
-
由 rofl0r 提交于
-
由 rofl0r 提交于
-
由 rofl0r 提交于
-
由 rofl0r 提交于
the prototype is defined with const gid_t* rather than const gid_t[]. it was already correctly defined in grp.h.
-
由 rofl0r 提交于
the macro was the wrong way round, additionally GNU defines __ prefixed versions, which are used by qemu.
-
由 rofl0r 提交于
this function is obsolete, however it's available as a syscall and as such qemu userspace emulation tries to forward it to the host kernel.
-
由 rofl0r 提交于
glibc exposes them from ucontext.h. since that header includes signal.h, it is safe to put them into bits/signal.h, if _GNU_SOURCE is defined.
-
由 rofl0r 提交于
thankfully these are all generic across archs. the DN_ macros are for usage with F_NOTIFY.
-
由 rofl0r 提交于
-
- 06 12月, 2012 7 次提交
-
-
由 rofl0r 提交于
these are also needed by qemu.
-
由 rofl0r 提交于
both kernel and glibc define it only on x86(_64).
-
由 rofl0r 提交于
this is needed for qemu, and since it differs for each arch it can't be circumvented easily by using a macro in CFLAGS.
-
由 Rich Felker 提交于
the issue is identical to the recent commit fixing the mips versions: despite other implementations doing this, it conflicts with the requirements of ISO C and it's a waste of time and code size.
-
由 Rich Felker 提交于
previously, everything was going through an intermediate conversion to long double, which caused the extern __fpclassifyl function to get invoked, preventing virtually all optimizations of these operations. with the new code, tests on constant float or double arguments compile to a constant 0 or 1, and tests on non-constant expressions are efficient. I may later add support for __builtin versions on compilers that support them.
-
由 Rich Felker 提交于
nothing in the standard requires or even allows the fenv state to be restored by longjmp. restoring the exception flags is not such a big deal since it's probably valid to clobber them completely, but restoring the rounding mode yields an observable side effect not sanctioned by ISO C. saving/restoring it also wastes a few cycles and 16 bytes of code. as for historical behavior, reportedly SGI IRIX did save/restore fenv, and this is where glibc and uClibc got the behavior from. a few other systems save/restore it too (on archs other than mips), even though this is apparently wrong. further details are documented here: http://www-personal.umich.edu/~williams/archive/computation/setjmp-fpmode.html as musl aims for standards conformance rather than coddling historical programs expecting non-conforming behavior, and as it's unlikely that any historical programs actually depend on the incorrect behavior (such programs would break on other archs, anyway), I'm making the change not to save/restore fenv on mips.
-
由 Rich Felker 提交于
due to some historical oddity, these are considered libc headers rather than kernel headers. the kernel used to provide them too, but it seems modern kernels do not install them, so let's just do the easiest thing and provide them. stripped-down versions provided by John Spencer.
-
- 05 12月, 2012 2 次提交
-
-
由 Rich Felker 提交于
apparently recent gcc versions have intentionally broken the traditional definition by treating it as a non-constant expression. the traditional definition may also be problematic for c++ programs.
-
由 Rich Felker 提交于
for some reason I have not been able to determine, gcc 3.2 rejects the array notation. this seems to be a gcc bug, but since it's easy to work around, let's do the workaround and avoid gratuitously requiring newer compilers.
-