| Commit message (Expand) | Author | Files | Lines |
|---|
| 2013-11-26 | adjust fallback INFINITY definition for FLT_EVAL_METHOD==2 case•••on archs with excess precision, the floating point constant 1e40f may
be evaluated such that it does not actually produce an infinity.
1e5000f is sufficiently large to produce an infinity for all supported
floating point formats. note that this definition of INFINITY is only
used for old or non-GNUC compilers anyway; despite being a portable,
conforming definition, it leads to erroneous warnings on many
compilers and thus using the builtin is preferred.
| Rich Felker | 1 | -1/+1 |
| 2013-11-26 | fix off-by-one length failure in strftime/wcsftime and improve error behavior•••these functions were spuriously failing in the case where the buffer
size was exactly the number of bytes/characters to be written,
including null termination. since these functions do not have defined
error conditions other than buffer size, a reasonable application may
fail to check the return value when the format string and buffer size
are known to be valid; such an application could then attempt to use a
non-terminated buffer.
in addition to fixing the bug, I have changed the error handling
behavior so that these functions always null-terminate the output
except in the case where the buffer size is zero, and so that they
always write as many characters as possible before failing, rather
than dropping whole fields that do not fit. this actually simplifies
the logic somewhat anyway.
| Rich Felker | 2 | -12/+16 |
| 2013-11-25 | remove duplicate includes from dynlink.c, strfmon.c and getaddrinfo.c | Szabolcs Nagy | 3 | -7/+0 |
| 2013-11-24 | restore type of NULL to void * except when used in C++ programs•••unfortunately this eliminates the ability of the compiler to diagnose
some dangerous/incorrect usage, but POSIX requires (as an extension to
the C language, i.e. CX shaded) that NULL have type void *. plain C
allows it to be defined as any null pointer constant.
the definition 0L is preserved for C++ rather than reverting to plain
0 to avoid dangerous behavior in non-conforming programs which use
NULL as a variadic sentinel. (it's impossible to use (void *)0 for C++
since C++ lacks the proper implicit pointer conversions, and other
popular alternatives like the GCC __null extension seem non-conforming
to the standard's requirements.)
| Rich Felker | 8 | -0/+33 |
| 2013-11-24 | shadow: Implement fgetspent | Michael Forney | 1 | -1/+10 |
| 2013-11-24 | shadow: Move spent parsing to internal function | Michael Forney | 2 | -31/+40 |
| 2013-11-24 | Fix dn_comp prototype and add stub•••This function is used by ping6 from iputils.
| Michael Forney | 2 | -1/+10 |
| 2013-11-24 | shadow: Implement putspent | Michael Forney | 2 | -5/+13 |
| 2013-11-24 | math: clean up __rem_pio2•••- remove the HAVE_EFFICIENT_IRINT case: fn is an exact integer, so
it can be converted to int32_t a bit more efficiently than with a
cast (the rounding mode change can be avoided), but musl does not
support this case on any arch.
- __rem_pio2: use double_t where possible
- __rem_pio2f: use less assignments to avoid stores on i386
- use unsigned int bit manipulation (and union instead of macros)
- use hexfloat literals instead of named constants
| Szabolcs Nagy | 3 | -71/+53 |
| 2013-11-24 | use 0 instead of NULL in headers where NULL is not defined•••some macros in sys/mtio.h and syslog.h used NULL without defining it
| Szabolcs Nagy | 2 | -3/+3 |
| 2013-11-23 | add O_TMPFILE flag, new in linux 3.11•••definition in linux:
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)
where __O_TMPFILE and O_DIRECTORY are arch specific
| Szabolcs Nagy | 6 | -0/+6 |
| 2013-11-23 | add TCP_NOTSENT_LOWAT tcp socket option, new in linux v3.12 | Szabolcs Nagy | 1 | -0/+1 |
| 2013-11-23 | add linux tcp state enums | Timo Teräs | 1 | -0/+12 |
| 2013-11-23 | add multicast structures from RFC 3678 to netinet/in.h•••and use _GNU_SOURCE || _BSD_SOURCE guards for all of the RFC 3678
namespace polluting things like glibc/uclibc does.
| Timo Teräs | 1 | -1/+42 |
| 2013-11-23 | Fix dn_expand pointer following | Michael Forney | 1 | -1/+1 |
| 2013-11-23 | putgrent: Add missing newline | Michael Forney | 1 | -0/+1 |
| 2013-11-23 | putgrent: Stop writing output on first failure•••This way, if an fprintf fails, we get an incomplete group entry rather
than a corrupted one.
| Michael Forney | 1 | -2/+3 |
| 2013-11-23 | strcmp: Remove unnecessary check for *r•••If *l == *r && *l, then by transitivity, *r.
| Michael Forney | 1 | -1/+1 |
| 2013-11-23 | timeradd/timersub: cast result to void to get rid of warnings•••previously:
timersub(&now, t, &diff);
warning: value computed is not used [-Wunused-value]
| rofl0r | 1 | -2/+2 |
| 2013-11-22 | fix and refactor child reaping logic in wordexp•••loop condition was incorrect and confusing and caused an infinite loop
when (broken) applications reaped the pid from a signal handler or
another thread before wordexp's call to waitpid could do so.
| Rich Felker | 1 | -6/+16 |
| 2013-11-22 | fix fd leak and case where fd 1 is already closed in wordexp | Rich Felker | 1 | -4/+4 |
| 2013-11-22 | fix resource exhaustion and zero-word cases in wordexp•••when WRDE_NOSPACE is returned, the we_wordv and we_wordc members must
be valid, because the interface contract allows them to return partial
results.
in the case of zero results (due either to resource exhaustion or a
zero-word input) the we_wordv array still should contain a terminating
null pointer and the initial we_offs null pointers. this is impossible
on resource exhaustion, so a correct application must presumably check
for a null pointer in we_wordv; POSIX however seems to ignore the
issue. the previous code may have crashed under this situation.
| Rich Felker | 1 | -8/+18 |
| 2013-11-22 | improve robustness of wordexp and fix handling of 0-word case•••avoid using exit status to determine if a shell error occurred, since
broken programs may install SIGCHLD handlers which reap all zombies,
including ones that don't belong to them. using clone and __WCLONE
does not seem to work for avoiding this problem since exec resets the
exit signal to SIGCHLD.
instead, the new code uses a dummy word at the beginning of the
shell's output, which is ignored, to determine whether the command was
executed successfully. this also fixes a corner case where a word
string containing zero words was interpreted as a single zero-length
word rather than no words at all. POSIX does not seem to require this
case to be supported anyway, though.
in addition, the new code uses the correct retry idiom for waitpid to
ensure that spurious STOP/CONT signals in the child and/or EINTR in
the parent do not prevent successful wait for the child, and blocks
signals in the child.
| Rich Felker | 1 | -11/+16 |
| 2013-11-21 | add legacy getloadavg api | Szabolcs Nagy | 2 | -0/+19 |
| 2013-11-20 | fix fd leak (missing close-on-exec) in getifaddrs | Rich Felker | 1 | -1/+1 |
| 2013-11-21 | math: add (obsolete) bsd drem and finite functions | Szabolcs Nagy | 5 | -0/+26 |
| 2013-11-21 | math: lgamma cleanup (simpler sin(pi*x) for the negative case)•••* simplify sin_pi(x) (don't care about inexact here, the result is
inexact anyway, and x is not so small to underflow)
* in lgammal add the previously removed special case for x==1 and
x==2 (to fix the sign of zero in downward rounding mode)
* only define lgammal on supported long double platforms
* change tgamma so the generated code is a bit smaller
| Szabolcs Nagy | 4 | -202/+110 |
| 2013-11-20 | fix the nominal type of LDBL_* limits on archs with ld64•••previously these macros wrongly had type double rather than long
double. I see no way an application could detect the error in C99, but
C11's _Generic can trivially detect it.
at the same time, even though these archs do not have excess
precision, the number of decimal places used to represent these
constants has been increased to 21 to be consistent with the decimal
representations used for the DBL_* macros.
| Rich Felker | 4 | -16/+16 |
| 2013-11-20 | write floating point limit constants to 21 significant decimal places•••this is enough to produce the correct value even if the constant is
interpreted as 80-bit extended precision, which matters on archs with
excess precision (FLT_EVAL_METHOD==2) under at least some
interpretations of the C standard. the shorter representations, while
correct if converted to the nominal precision at translation time,
could produce an incorrect value at extended precision, yielding
results such as (double)DBL_MAX != DBL_MAX.
| Rich Felker | 2 | -10/+10 |
| 2013-11-11 | iswspace: fix handling of 0 | rofl0r | 1 | -2/+1 |
| 2013-11-09 | fix harmless inconsistency in semtimedop•••this should not matter since the reality is that either all the sysv
sem syscalls are individual syscalls, or all of them are multiplexed
on the SYS_ipc syscall (depending on arch). but best to be consistent
anyway.
| Rich Felker | 1 | -1/+1 |
| 2013-11-09 | implement semtimedop•••this is a Linux-specific extension to the sysv semaphore api.
| Rich Felker | 2 | -0/+14 |
| 2013-11-09 | adjust sys/wait.h not to produde errors in strict ISO C feature profile•••siginfo_t is not available from signal.h when the strict ISO C feature
profile (e.g. passing -std=c99 to gcc without defining any other
feature test macros) is used, but the type is needed to declare
waitid. using sys/wait.h (or any POSIX headers) in strict ISO C mode
is an application bug, but in the interest of compatibility, it's best
to avoid producing gratuitous errors. the simplest fix I could find is
suppressing the declaration of waitid (and also signal.h inclusion,
since it's not needed for anything else) in this case, while still
exposing everything else in sys/wait.h
| Rich Felker | 1 | -3/+7 |
| 2013-11-08 | remove O_NOFOLLOW from __map_file used for time zone file loading•••it's not clear why I originally wrote O_NOFOLLOW into this; I suspect
the reason was with an aim of making the function more general for
mapping partially or fully untrusted files provided by the user.
however, the timezone code already precludes use of absolute or
relative pathnames in suid/sgid programs, and disallows .. in
pathnames which are relative to one of the system timezone locations,
so there is no threat of opening a symlink which is not trusted by
appropriate user. since some users may wish to put symbolic links in
the zoneinfo directories to alias timezones, it seems preferable to
allow this.
| Rich Felker | 1 | -1/+1 |
| 2013-11-08 | fix handling of overly-long TZ environment variable values•••the rest of the code is not prepared to handle an empty TZ string, so
falling back to __gmt ("GMT"), just as if TZ had been blank or unset,
is the preferable action.
| Rich Felker | 1 | -1/+1 |
| 2013-11-04 | timezone parser: fix iteration over search dir paths•••try+l points to \0, so only one iteration was ever tried.
| rofl0r | 1 | -1/+1 |
| 2013-11-04 | timezone parser: fix offset to transition table in 64bit code path•••we need to skip to the second TZif header, which starts at
skip+44, and then skip another header (20 bytes) plus the following
6 32bit values.
| rofl0r | 1 | -1/+1 |
| 2013-11-04 | fix timezone parser code crashing on 64bit sys•••if sizeof(time_t) == 8, this code path was missing the correct
offset into the zoneinfo file, using the header magic to do
offset calculations.
the 6 32bit fields to be read start at offset 20.
| rofl0r | 1 | -1/+1 |
| 2013-11-02 | fix regression in inet_aton due to misinterpretation of __ipparse return•••inet_aton returns a boolean success value, whereas __ipparse returns 0
on success and -1 on failure. also change the conditional in inet_addr
to be consistent with other uses of __ipparse where only negative
values are treated as failure.
| Rich Felker | 2 | -3/+3 |
| 2013-11-01 | simplify faccessat AT_EACCESS path and eliminate resource dependence•••now that we're waiting for the exit status of the child process, the
result can be conveyed in the exit status rather than via a pipe.
since the error value might not fit in 7 bits, a table is used to
translate possible meaningful error values to small integers.
| Rich Felker | 1 | -14/+21 |
| 2013-11-01 | fix faccessat AT_EACCESS path not to leave zombie processes•••I mistakenly assumed that clone without a signal produced processes
that would not become zombies; however, waitpid with __WCLONE is
required to release their pids.
| Rich Felker | 1 | -2/+6 |
| 2013-10-30 | fix inttypes.h PRI and SCN macros for [u]intptr_t types•••while using "l" unconditionally gave the right behavior due to
matching sizes/representations, it was technically UB and produced
compiler warnings with format string checking.
| Rich Felker | 1 | -11/+13 |
| 2013-10-29 | POSIX conformance fix: define struct entry in search.h | Szabolcs Nagy | 2 | -9/+9 |
| 2013-10-28 | fenv: fix i386 fesetround for sse•••i386 fenv code checks __hwcap for sse support, but in fesetround the sse
code was unconditionally jumped over after the test so the sse rounding
mode was never set.
| Szabolcs Nagy | 1 | -1/+1 |
| 2013-10-28 | math: extensive log*.c cleanup•••The log, log2 and log10 functions share a lot of code and to a lesser
extent log1p too. A small part of the code was kept separately in
__log1p.h, but since it did not capture much of the common code and
it was inlined anyway, it did not solve the issue properly. Now the
log functions have significant code duplication, which may be resolved
later, until then they need to be modified together.
logl, log10l, log2l, log1pl:
* Fix the sign when the return value should be -inf.
* Remove the volatile hack from log10l (seems unnecessary)
log1p, log1pf:
* Change the handling of small inputs: only |x|<2^-53 is special
(then it is enough to return x with the usual subnormal handling)
this fixes the sign of log1p(0) in downward rounding.
* Do not handle the k==0 case specially (other than skipping the
elaborate argument reduction)
* Do not handle 1+x close to power-of-two specially (this code was
used rarely, did not give much speed up and the precision wasn't
better than the general)
* Fix the correction term formula (c=1-(u-x) was used incorrectly
when x<1 but (double)(x+1)==2, this was not a critical issue)
* Use the exact same method for calculating log(1+f) as in log
(except in log1p the c correction term is added to the result).
log, logf, log10, log10f, log2, log2f:
* Use double_t and float_t consistently.
* Now the first part of log10 and log2 is identical to log (until the
return statement, hopefully this makes maintainence easier).
* Most special case formulas were removed (close to power-of-two and
k==0 cases), they increase the code size without providing precision
or performance benefits (and obfuscate the code).
Only x==1 is handled specially so in downward rounding mode the
sign of zero is correct (the general formula happens to give -0).
* For x==0 instead of -1/0.0 or -two54/0.0, return -1/(x*x) to force
raising the exception at runtime.
* Arg reduction code is changed (slightly simplified)
* The thresholds for arg reduction to [sqrt(2)/2,sqrt(2)] are now
consistently the [0x3fe6a09e00000000,0x3ff6a09dffffffff] and the
[0x3f3504f3,0x3fb504f2] intervals for double and float reductions
respectively (the exact threshold values are not critical)
* Remove the obsolete comment for the FLT_EVAL_METHOD!=0 case in log2f
(The same code is used for all eval methods now, on i386 slightly
simpler code could be used, but we have asm there anyway)
all:
* Fix signed int arithmetics (using unsigned for bitmanipulation)
* Fix various comments
| Szabolcs Nagy | 14 | -583/+369 |
| 2013-10-25 | add legacy ftime function and sys/timeb.h•••despite being marked legacy, this was specified by SUSv3 as part of
the XSI option; only the most recent version of the standard dropped
it. reportedly there's actual code using it.
| Rich Felker | 2 | -0/+34 |
| 2013-10-23 | fix inet_pton•••* parse IPv4 dotted-decimal correctly (without strtoul, no leading zeros)
* disallow single leading ':' in IPv6 address
* allow at most 4 hex digits in IPv6 address (according to RFC 2373)
* have enough hex fields in IPv4 mapped IPv6 address
* disallow leading zeros in IPv4 mapped IPv6 address
| Szabolcs Nagy | 1 | -26/+19 |
| 2013-10-22 | fix __ipparse to parse the generic numbers-and-dots IPv4 format correctly•••* allow at most 4 parts
* bounds check the parts correctly
* disallow leading whitespace and sign
* check the address family before falling back to IPv6
| Szabolcs Nagy | 1 | -5/+12 |
| 2013-10-22 | fix inet_aton to accept the generic "numbers-and-dots" IPv4 address format | Szabolcs Nagy | 1 | -1/+4 |
| 2013-10-21 | split inet_addr and inet_ntoa back into their own files•••despite being practically deprecated, these functions are still part
of the standard and thus cannot reside in a file that also contains
namespace pollution. this reverts some of the changes made in commit
e40f48a421a9176e3e298b5bac75f0355b219e58.
| Rich Felker | 3 | -16/+21 |
