summaryrefslogtreecommitdiff
path: root/include/unistd.h
AgeCommit message (Collapse)AuthorFilesLines
2013-07-27a few more fixes for unistd/sysconf feature reportingRich Felker1-0/+1
2013-07-26report presence of ADV and MSG options in unistd.h and sysconfRich Felker1-0/+2
2013-07-26report that posix_spawn is supported in unistd.h and sysconfRich Felker1-0/+1
2013-06-26document in sysconf and unistd.h that per-thread cpu clocks existRich Felker1-0/+1
2013-04-02re-add useconds_trofl0r1-0/+1
this type was removed back in 5243e5f1606a9c6fcf01414e , because it was removed from the XSI specs. however some apps use it. since it's in the POSIX reserved namespace, we can expose it unconditionally.
2013-01-18use a common definition of NULL as 0L for C and C++Rich Felker1-6/+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.
2012-12-10syscall() declaration belongs in unistd.h, not sys/syscall.hRich Felker1-0/+1
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.
2012-12-06unistd.h: fix wrong type for gid_t argumentrofl0r1-1/+1
the prototype is defined with const gid_t* rather than const gid_t[]. it was already correctly defined in grp.h.
2012-11-11report support of TPS option in unistd.h and sysconfRich Felker1-0/+1
also update another newish feature in sysconf, stackaddr
2012-11-01avoid breakage if somebody wrongly defines empty feature test macrosRich Felker1-1/+1
2012-09-30define some _POSIX_* macros that were omitted; required for XSI conformanceRich Felker1-0/+3
2012-09-29always expose dup3 and pipe2Rich Felker1-2/+2
they will be in the next version of POSIX
2012-09-16add clock_adjtime, remap_file_pages, and syncfs syscall wrappersRich Felker1-0/+1
patch by Justin Cormack, with slight modification
2012-09-09add setdomainname syscall, fix getdomainname (previously a stub)Rich Felker1-0/+1
2012-09-08add acct, accept4, setns, and dup3 syscalls (linux extensions)Rich Felker1-0/+2
based on patch by Justin Cormack
2012-09-07default features: make musl usable without feature test macrosRich Felker1-12/+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-06further use of _Noreturn, for non-plain-C functionsRich Felker1-1/+8
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.
2012-09-06use restrict everywhere it's required by c99 and/or posix 2008Rich Felker1-3/+9
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-08-15improve headers to better deal with removed-in-posix-2008 featuresRich Felker1-2/+6
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.
2012-07-23add pipe2 syscallRich Felker1-0/+1
based on patch by orc and Isaac Dunham, with some details fixed.
2012-06-04_GNU_SOURCE is supposed to imply _LARGEFILE64_SOURCERich Felker1-1/+1
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.
2012-06-02declare environ in unistd.h when _GNU_SOURCE feature test macro is usedRich Felker1-0/+1
lots of broken programs expect this, and it's gotten to the point of being a troubleshooting FAQ topic. best to just fix it.
2012-05-22remove everything related to forkallRich Felker1-1/+0
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.
2012-05-22some feature test fixes for unistd.hRich Felker1-16/+16
2012-05-22_GNU_SOURCE implies all BSD features except ones GNU rejectsRich Felker1-1/+1
2012-05-22various header cleanups, some related to _BSD_SOURCE additionRich Felker1-11/+4
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.
2012-05-22support _BSD_SOURCE feature test macroRich Felker1-3/+17
patch by Isaac Dunham. matched closely (maybe not exact) to glibc's idea of what _BSD_SOURCE should make visible.
2012-05-20move getpass decl to the right placeRich Felker1-0/+1
2012-05-04add support for ugly *64 functions with _LARGEFILE64_SOURCERich Felker1-0/+10
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.
2012-04-22implement getusershell, etc. legacy functionsRich Felker1-0/+3
I actually wrote these a month ago but forgot to integrate them. ugly, probably-harmful-to-use functions, but some legacy apps want them...
2012-04-22getdtablesize is not standard; move it to its correct spot in unistd.hRich Felker1-1/+1
2012-04-22add getresuid and getresgid syscall wrappersRich Felker1-0/+2
2012-04-18legacy junk compatibility grab-bagRich Felker1-0/+2
- 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-17add get_current_dir_name functionRich Felker1-0/+1
2011-09-13fix various errors in function signatures/prototypes found by nszRich Felker1-3/+3
2011-08-12implement forkallRich Felker1-0/+1
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.
2011-04-27correct variadic prototypes for execl* familyRich Felker1-3/+3
the old versions worked, but conflicted with programs which declared their own prototypes and generated warnings with some versions of gcc.
2011-04-13fix prototypes/signature for setgroups, etc.Rich Felker1-1/+1
2011-04-03prototype getdtablesize (nonstandard function)Rich Felker1-0/+1
2011-04-03add setresuid/setresgid functions (nonstandard)Rich Felker1-0/+2
2011-04-01remove obsolete and useless useconds_t typeRich Felker1-3/+2
2011-02-27implement fexecveRich Felker1-0/+1
2011-02-19prototypes for brk and sbrkRich Felker1-0/+2
2011-02-15feature test support in unistd.hRich Felker1-23/+27
2011-02-12initial check-in, version 0.5.0v0.5.0Rich Felker1-0/+464
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-16 23:48:51 +0000