- 05 9月, 2013 21 次提交
-
-
由 Szabolcs Nagy 提交于
libc.h is only for weak_alias so include it directly where it is used
-
由 Szabolcs Nagy 提交于
acosh(x) is invalid for x<1, acoshf tried to be clever using signed comparisions to handle all x<2 the same way, but the formula was wrong on large negative values.
-
由 Szabolcs Nagy 提交于
copy the fix from i386: return -1 instead of exp2l(x)-1 when x <= -65
-
由 Szabolcs Nagy 提交于
-
由 Szabolcs Nagy 提交于
there were two problems: * omitted underflow on subnormal results: exp2l(-16383.5) was calculated as sqrt(2)*2^-16384, the last bits of sqrt(2) are zero so the down scaling does not underflow eventhough the result is in subnormal range * spurious underflow for subnormal inputs: exp2l(0x1p-16400) was evaluated as f2xm1(x)+1 and f2xm1 raised underflow (because inexact subnormal result) the first issue is fixed by raising underflow manually if x is in (-32768,-16382] and not integer (x-0x1p63+0x1p63 != x) the second issue is fixed by treating x in (-0x1p64,0x1p64) specially for these fixes the special case handling was completely rewritten
-
由 Szabolcs Nagy 提交于
-
由 Szabolcs Nagy 提交于
only fma used these macros and the explicit union is clearer
-
由 Szabolcs Nagy 提交于
-
由 Szabolcs Nagy 提交于
* use new ldshape union consistently * add ld128 support to frexpl * simplify sqrtl comment (ld64 is not just arm)
-
由 Szabolcs Nagy 提交于
remove STRICT_ASSIGN (c99 semantics is assumed) and use the conventional union to prepare the scaling factor (so libm.h is no longer needed)
-
由 Szabolcs Nagy 提交于
in lgammal don't handle 1 and 2 specially, in fma use the new ldshape union instead of ld80 one.
-
由 Szabolcs Nagy 提交于
* use float_t and double_t * cleanup subnormal handling * bithacks according to the new convention (ldshape for long double and explicit unions for float and double)
-
由 Szabolcs Nagy 提交于
* don't care about inexact flag * use double_t and float_t (faster, smaller, more precise on x86) * exp: underflow when result is zero or subnormal and not -inf * exp2: underflow when result is zero or subnormal and not exact * expm1: underflow when result is zero or subnormal * expl: don't underflow on -inf * exp2: fix incorrect comment * expm1: simplify special case handling and overflow properly * expm1: cleanup final scaling and fix negative left shift ub (twopk)
-
由 Szabolcs Nagy 提交于
ld128 support was added to internal kernel functions (__cosl, __sinl, __tanl, __rem_pio2l) from freebsd (not tested, but should be a good start for when ld128 arch arrives) __rem_pio2l had some code cleanup, the freebsd ld128 code seems to gather the results of a large reduction with precision loss (fixed the bug but a todo comment was added for later investigation) the old copyright was removed from the non-kernel wrapper functions (cosl, sinl, sincosl, tanl) since these are trivial and the interesting parts and comments had been already rewritten.
-
由 Szabolcs Nagy 提交于
* added ld128 support from freebsd fdlibm (untested) * using new ldshape union instead of IEEEl2bits * inexact status flag is not supported
-
由 Szabolcs Nagy 提交于
method: if there is a large difference between the scale of x and y then the larger magnitude dominates, otherwise reduce x,y so the argument of sqrt (x*x+y*y) does not overflow or underflow and calculate the argument precisely using exact multiplication. If the argument has less error than 1/sqrt(2) ~ 0.7 ulp, then the result has less error than 1 ulp in nearest rounding mode. the original fdlibm method was the same, except it used bit hacks instead of dekker-veltkamp algorithm, which is problematic for long double where different representations are supported. (the new hypot and hypotl code should be smaller and faster on 32bit cpu archs with fast fpu), the new code behaves differently in non-nearest rounding, but the error should be still less than 2ulps. ld80 and ld128 are supported
-
由 Szabolcs Nagy 提交于
* results are exact * modfl follows truncl (raises inexact flag spuriously now) * modf and modff only had cosmetic cleanup * remainder is just a wrapper around remquo now * using iterative shift+subtract for remquo and fmod * ld80 and ld128 are supported as well
-
由 Szabolcs Nagy 提交于
* faster, smaller, cleaner implementation than the bit hacks of fdlibm * use arithmetics like y=(double)(x+0x1p52)-0x1p52, which is an integer neighbor of x in all rounding modes (0<=x<0x1p52) and only use bithacks when that's faster and smaller (for float it usually is) * the code assumes standard excess precision handling for casts * long double code supports both ld80 and ld128 * nearbyint is not changed (it is a wrapper around rint)
-
由 Szabolcs Nagy 提交于
use -1/(x*x) instead of -1/(x+0) to return -inf, -0+0 is -0 in downward rounding mode
-
由 Szabolcs Nagy 提交于
* consistent code style * explicit union instead of typedef for double and float bit access * turn FENV_ACCESS ON to make 0/0.0f raise invalid flag * (untested) ld128 version of ilogbl (used by logbl which has ld128 support)
-
由 Szabolcs Nagy 提交于
new ldshape union, ld128 support is kept, code that used the old ldshape union was rewritten (IEEEl2bits union of freebsd libm is not touched yet) ld80 __fpclassifyl no longer tries to handle invalid representation
-
- 04 9月, 2013 1 次提交
-
-
由 Rich Felker 提交于
-
- 03 9月, 2013 3 次提交
-
-
由 Rich Felker 提交于
switch to the new __block_all_sigs/__restore_sigs internal API to clean up the code too.
-
由 Rich Felker 提交于
this protects against deadlock from spurious signals (e.g. sent by another process) arriving after the controlling thread releases the other threads from the sync operation.
-
由 Rich Felker 提交于
the head pointer was not being reset between calls to synccall, so any use of this interface more than once would build the linked list incorrectly, keeping the (now invalid) list nodes from the previous call.
-
- 02 9月, 2013 1 次提交
-
-
由 Rich Felker 提交于
-
- 01 9月, 2013 7 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
clone will pass the return value of the start function to SYS_exit anyway; there's no need to call the syscall directly.
-
由 Rich Felker 提交于
the wide variant was missed in the previous commit.
-
由 Rich Felker 提交于
invalid format strings invoke undefined behavior, so this is not a conformance issue, but it's nicer for scanf to report the error safely instead of calling free on a potentially-uninitialized pointer or a pointer to memory belonging to the caller.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
rather than allocating a PATH_MAX-sized buffer when the caller does not provide an output buffer, work first with a PATH_MAX-sized temp buffer with automatic storage, and either copy it to the caller's buffer or strdup it on success. this not only avoids massive memory waste, but also avoids pulling in free (and thus the full malloc implementation) unnecessarily in static programs.
-
由 Rich Felker 提交于
this avoids failure if the file is not readable and avoids odd behavior for device nodes, etc. on old kernels that lack O_PATH, the old behavior (O_RDONLY) will naturally happen as the fallback.
-
- 31 8月, 2013 6 次提交
-
-
由 Rich Felker 提交于
DESTDIR was wrongly included in the symlink contents.
-
由 Rich Felker 提交于
commit 07827d1a seems to have introduced this issue. sigqueue is called from the synccall core, at which time, even implementation-internal signals are blocked. however, pthread_sigmask removes the implementation-internal signals from the old mask before returning, so that a process which began life with them blocked will not be able to save a signal mask that has them blocked, possibly causing them to become re-blocked later. however, this was causing sigqueue to unblock the implementation-internal signals during synccall, leading to deadlock.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
the BSD and GNU versions of this structure differ, so exposing it in the default _BSD_SOURCE profile is possibly problematic. both versions could be simultaneously supported with anonymous unions if needed in the future, but for now, just omitting it except under _GNU_SOURCE should be safe.
-
由 Rich Felker 提交于
-
- 28 8月, 2013 1 次提交
-
-
由 Rich Felker 提交于
I originally added this warning option based on a misunderstanding of how it works. it does not warn whenever the destination of the cast has stricter alignment; it only warns in cases where misaligned dereference could lead to a fault. thus, it's essentially a no-op for i386, which had me wrongly believing the code was clean for this warning level. on other archs, numerous diagnostic messages are produced, and all of them are false-positives, so it's better just not to use it.
-