summaryrefslogtreecommitdiff
path: root/include/time.h
AgeCommit message (Collapse)AuthorLines
2013-06-08add clock id macros for a number of new(ish) Linux-specific clocksRich Felker-0/+6
arguably CLOCK_MONOTONIC should be redirected to CLOCK_BOOTTIME with a fallback for old kernels that don't support it, since Linux's CLOCK_BOOTTIME semantics seem to match the spirit of the POSIX requirements for CLOCK_MONOTONIC better than Linux's version of CLOCK_MONOTONIC does. however, this is a change that would require further discussion and research, so for now, I'm simply making them all available.
2013-06-08fix the type of CLOCKS_PER_SEC to match new clock_t typeRich Felker-1/+1
originally it was right on 32-bit archs and wrong on 64-bit, but after recent changes it was wrong everywhere. with this commit, it's now right everywhere.
2013-06-07improve handling of nonstandard fields in struct tmRich Felker-4/+5
defining tm_gmtoff and tm_zone as macros was breaking some application code that used these names for its own purposes.
2013-04-02make tm_zone etc visible under _GNU_SOURCErofl0r-1/+1
2013-01-18use a common definition of NULL as 0L for C and C++Rich Felker-7/+1
the historical mess of having different definitions for C and C++ comes from the historical C definition as (void *)0 and the fact that (void *)0 can't be used in C++ because it does not convert to other pointer types implicitly. however, using plain 0 in C++ exposed bugs in C++ programs that call variadic functions with NULL as an argument and (wrongly; this is UB) expect it to arrive as a null pointer. on 64-bit machines, the high bits end up containing junk. glibc dodges the issue by using a GCC extension __null to define NULL; this is observably non-conforming because a conforming application could observe the definition of NULL via stringizing and see that it is neither an integer constant expression with value zero nor such an expression cast to void. switching to 0L eliminates the issue and provides compatibility with broken applications, since on all musl targets, long and pointers have the same size, representation, and argument-passing convention. we could maintain separate C and C++ definitions of NULL (i.e. just use 0L on C++ and use (void *)0 on C) but after careful analysis, it seems extremely difficult for a C program to even determine whether NULL has integer or pointer type, much less depend in subtle, unintentional ways, on whether it does. C89 seems to have no way to make the distinction. on C99, the fact that (int)(void *)0 is not an integer constant expression, along with subtle VLA/sizeof semantics, can be used to make the distinction, but many compilers are non-conforming and give the wrong result to this test anyway. on C11, _Generic can trivially make the distinction, but it seems unlikely that code targetting C11 would be so backwards in caring which definition of NULL an implementation uses. as such, the simplest path of using the same definition for NULL in both C and C++ was chosen. the #undef directive was also removed so that the compiler can catch and give a warning or error on redefinition if buggy programs have defined their own versions of NULL prior to inclusion of standard headers.
2013-01-04time.h: add BSD aliases for otherwise internal struct tm membersrofl0r-0/+4
2012-09-07default features: make musl usable without feature test macrosRich Felker-5/+1
the old behavior of exposing nothing except plain ISO C can be obtained by defining __STRICT_ANSI__ or using a compiler option (such as -std=c99) that predefines it. the new default featureset is POSIX with XSI plus _BSD_SOURCE. any explicit feature test macros will inhibit the default. installation docs have also been updated to reflect this change.
2012-09-06use restrict everywhere it's required by c99 and/or posix 2008Rich Felker-8/+14
to deal with the fact that the public headers may be used with pre-c99 compilers, __restrict is used in place of restrict, and defined appropriately for any supported compiler. we also avoid the form [restrict] since older versions of gcc rejected it due to a bug in the original c99 standard, and instead use the form *restrict.
2012-06-13revert one change in time.h; no evidence BSD_SOURCE should expose these..Rich Felker-1/+1
2012-06-13fix feature test macros in time.hRich Felker-5/+2
stime is not _XOPEN_SOURCE, and some functions were missing with _BSD_SOURCE..
2012-06-13add timegm function (inverse of gmtime), nonstandardRich Felker-0/+3
2012-05-22support _BSD_SOURCE feature test macroRich Felker-2/+4
patch by Isaac Dunham. matched closely (maybe not exact) to glibc's idea of what _BSD_SOURCE should make visible.
2012-04-18legacy junk compatibility grab-bagRich Felker-0/+5
- add the rest of the junk traditionally in sys/param.h - add prototypes for some nonstandard functions - add _GNU_SOURCE to their source files so the compiler can check proto
2012-02-06more locale_t interfaces (string stuff) and header updatesRich Felker-0/+3
this should be everything except for some functions where the non-_l version isn't even implemented yet (mainly some non-ISO-C wcs* functions).
2011-09-26cleanup various minor issues reported by nszRich Felker-1/+0
the changes to syscall_ret are mostly no-ops in the generated code, just cleanup of type issues and removal of some implementation-defined behavior. the one exception is the change in the comparison value, which is fixed so that 0xf...f000 (which in principle could be a valid return value for mmap, although probably never in reality) is not treated as an error return.
2011-09-13fix various errors in function signatures/prototypes found by nszRich Felker-1/+1
2011-02-15fix another error from header cleanup, missing size_t in time.hRich Felker-1/+1
2011-02-14more header cleanup and conformance fixes - locale.h, time.hRich Felker-34/+35
2011-02-12initial check-in, version 0.5.0v0.5.0Rich Felker-0/+113
generated by cgit v1.2.1 (git 2.18.0) at 2024-04-26 16:19:40 +0000