- 12 11月, 2012 1 次提交
-
-
由 Rich Felker 提交于
also update another newish feature in sysconf, stackaddr
-
- 01 11月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 30 9月, 2012 2 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
they will be in the next version of POSIX
-
- 17 9月, 2012 1 次提交
-
-
由 Rich Felker 提交于
patch by Justin Cormack, with slight modification
-
- 10 9月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 09 9月, 2012 1 次提交
-
-
由 Rich Felker 提交于
based on patch by Justin Cormack
-
- 08 9月, 2012 1 次提交
-
-
由 Rich Felker 提交于
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.
-
- 07 9月, 2012 2 次提交
-
-
由 Rich Felker 提交于
note that POSIX does not specify these functions as _Noreturn, because POSIX is aligned with C99, not the new C11 standard. when POSIX is eventually updated to C11, it will almost surely give these functions the _Noreturn attribute. for now, the actual _Noreturn keyword is not used anyway when compiling with a c99 compiler, which is what POSIX requires; the GCC __attribute__ is used instead if it's available, however. in a few places, I've added infinite for loops at the end of _Noreturn functions to silence compiler warnings. presumably __buildin_unreachable could achieve the same thing, but it would only work on newer GCCs and would not be portable. the loops should have near-zero code size cost anyway. like the previous _Noreturn commit, this one is based on patches contributed by philomath.
-
由 Rich Felker 提交于
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.
-
- 16 8月, 2012 1 次提交
-
-
由 Rich Felker 提交于
with this patch, setting _POSIX_SOURCE, or setting _POSIX_C_SOURCE or _XOPEN_SOURCE to an old version, will bring back the interfaces that were removed in POSIX 2008 - at least the ones i've covered so far, which are gethostby*, usleep, and ualarm. if there are other functions still in widespread use that were removed for which similar changes would be beneficial, they can be added just like this.
-
- 24 7月, 2012 1 次提交
-
-
由 Rich Felker 提交于
based on patch by orc and Isaac Dunham, with some details fixed.
-
- 04 6月, 2012 1 次提交
-
-
由 Rich Felker 提交于
this is ugly and stupid, but now that the *64 symbol names exist, a lot of broken GNU software detects them in configure, then either breaks during build due to missing off64_t definition, or attempts to compile without function declarations/prototypes. "fixing" it here is easier than telling everyone to add yet another feature test macro to their builds.
-
- 03 6月, 2012 1 次提交
-
-
由 Rich Felker 提交于
lots of broken programs expect this, and it's gotten to the point of being a troubleshooting FAQ topic. best to just fix it.
-
- 23 5月, 2012 5 次提交
-
-
由 Rich Felker 提交于
i made a best attempt, but the intended semantics of this function are fundamentally contradictory. there is no consistent way to handle ownership of locks when forking a multi-threaded process. the code could have worked by accident for programs that only used normal mutexes and nothing else (since they don't actually store or care about their owner), but that's about it. broken-by-design interfaces that aren't even in glibc (only solaris) don't belong in musl.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
there is no reason to avoid multiple identical macro definitions; this is perfectly legal C, and even with the maximal warning options enabled, gcc does not issue any warning for it.
-
由 Rich Felker 提交于
patch by Isaac Dunham. matched closely (maybe not exact) to glibc's idea of what _BSD_SOURCE should make visible.
-
- 21 5月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 04 5月, 2012 1 次提交
-
-
由 Rich Felker 提交于
musl does not support legacy 32-bit-off_t whatsoever. off_t is always 64 bit, and correct programs that use off_t and the standard functions will just work out of the box. (on glibc, they would require -D_FILE_OFFSET_BITS=64 to work.) however, some programs instead define _LARGEFILE64_SOURCE and use alternate versions of all the standard types and functions with "64" appended to their names. we do not want code to actually get linked against these functions (it's ugly and inconsistent), so macros are used instead of prototypes with weak aliases in the library itself. eventually the weak aliases may be added at the library level for the sake of using code that was originally built against glibc, but the macros will still be the desired solution in the headers.
-
- 23 4月, 2012 2 次提交
-
-
由 Rich Felker 提交于
I actually wrote these a month ago but forgot to integrate them. ugly, probably-harmful-to-use functions, but some legacy apps want them...
-
由 Rich Felker 提交于
-
- 22 4月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 19 4月, 2012 1 次提交
-
-
由 Rich Felker 提交于
- 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
-
- 18 2月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 14 9月, 2011 1 次提交
-
-
由 Rich Felker 提交于
-
- 12 8月, 2011 1 次提交
-
-
由 Rich Felker 提交于
this is a "nonstandard" function that was "rejected" by POSIX, but nonetheless had its behavior documented in the POSIX rationale for fork. it's present on solaris and possibly some other systems, and duplicates the whole calling process, not just a single thread. glibc does not have this function. it should not be used in programs intending to be portable, but may be useful for testing, checkpointing, etc. and it's an interesting (and quite small) example of the usefulness of the __synccall framework originally written to work around deficiencies in linux's setuid syscall.
-
- 28 4月, 2011 1 次提交
-
-
由 Rich Felker 提交于
the old versions worked, but conflicted with programs which declared their own prototypes and generated warnings with some versions of gcc.
-
- 13 4月, 2011 1 次提交
-
-
由 Rich Felker 提交于
-
- 04 4月, 2011 2 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
- 02 4月, 2011 1 次提交
-
-
由 Rich Felker 提交于
-
- 27 2月, 2011 1 次提交
-
-
由 Rich Felker 提交于
-
- 19 2月, 2011 1 次提交
-
-
由 Rich Felker 提交于
-
- 16 2月, 2011 1 次提交
-
-
由 Rich Felker 提交于
-
- 12 2月, 2011 1 次提交
-
-
由 Rich Felker 提交于
-