about summary refs log tree commit diff
path: root/arch/x86_64/bits
Commit message (Collapse)AuthorAgeFilesLines
* move F_DUPFD_CLOEXEC out of bitsRich Felker2012-04-151-2/+0
| | | | | | fcntl values 1024 and up are universal, arch-independent. later I'll add some of the other linux-specific ones for notify, leases, pipe size, etc. here too.
* add F_SETSIG and F_GETSIG (linux specific) to fcntl.hRich Felker2012-04-151-0/+2
| | | | F_* is in the reserved namespace so no feature test is needed
* fix DECIMAL_DIG definitionsRich Felker2012-03-211-0/+2
| | | | | | | | | | | | | DECIMAL_DIG is not the same as LDBL_DIG type_DIG is the maximimum number of decimal digits that can survive a round trip from decimal to type and back to decimal. DECIMAL_DIG is the minimum number of decimal digits required in order for any floating point type to survive the round trip to decimal and back, and it is generally larger than LDBL_DIG. since the exact formula is non-trivial, and defining it larger than necessary may be legal but wasteful, just define the right value in bits/float.h.
* add float_t and double_t to math.hRich Felker2012-02-151-0/+3
|
* replace bad cancellation cleanup abi with a sane oneRich Felker2012-02-091-6/+0
| | | | | | | | | | | | | | | | | | | | | | the old abi was intended to duplicate glibc's abi at the expense of being ugly and slow, but it turns out glib was not even using that abi except on non-gcc-compatible compilers (which it doesn't even support) and was instead using an exceptions-in-c/unwind-based approach whose abi we could not duplicate anyway without nasty dwarf2/unwind integration. the new abi is copied from a very old glibc abi, which seems to still be supported/present in current glibc. it avoids all unwinding, whether by sjlj or exceptions, and merely maintains a linked list of cleanup functions to be called from the context of pthread_exit. i've made some care to ensure that longjmp out of a cleanup function should work, even though it is not required to. this change breaks abi compatibility with programs which were using pthread cancellation, which is unfortunate, but that's why i'm making the change now rather than later. considering that most pthread features have not been usable until recently anyway, i don't see it as a major issue at this point.
* don't define wchar_t on c++Rich Felker2011-10-151-0/+2
| | | | | | it's a keyword in c++ (wtf). i'm not sure this is the cleanest solution; it might be better to avoid ever defining __NEED_wchar_t on c++. but in any case, this works for now.
* fix x86_64 user.h (previously was just a copy of i386)Rich Felker2011-09-221-48/+13
|
* wrong __WORDSIZE in x86_64 headerRich Felker2011-09-221-1/+1
|
* update syscalls with off_t arguments to handle argument alignment, if neededRich Felker2011-09-211-1/+2
| | | | | | the arm syscall abi requires 64-bit arguments to be aligned on an even register boundary. these new macros facilitate meeting the abi requirement without imposing significant ugliness on the code.
* fix the definition of struct statvfs to match lsb abiRich Felker2011-09-191-14/+6
| | | | | at the same time, make struct statfs match the traditional definition and make it more useful, especially the fsid_t stuff.
* cleanup redundancy in bits/signal.h versionsRich Felker2011-09-191-129/+9
|
* fix the type of wchar_t on arm; support wchar_t varying with archRich Felker2011-09-191-0/+4
| | | | | | | | | | | | | | really wchar_t should never vary, but the ARM EABI defines it as an unsigned 32-bit int instead of a signed one, and gcc follows this nonsense. thus, to give a conformant environment, we have to follow (otherwise L""[0] and L'\0' would be 0U rather than 0, but the application would be unaware due to a mismatched definition for WCHAR_MIN and WCHAR_MAX, and Bad Things could happen with respect to signed/unsigned comparisons, promotions, etc.). fortunately no rules are imposed by the C standard on the relationship between wchar_t and wint_t, and WEOF has type wint_t, so we can still make wint_t always-signed and use -1 for WEOF.
* cleanup more bits cruft (sysmacros and socket)Rich Felker2011-09-182-207/+0
|
* more bits junk (tcp.h)Rich Felker2011-09-181-1/+0
|
* move invariant netinet/in.h stuff out of bits/in.hRich Felker2011-09-181-145/+0
|
* typo in macro definitions for x86_64Rich Felker2011-08-141-1/+1
|
* socket headers macro adjustment - workaround for buggy programsRich Felker2011-07-211-1/+1
| | | | some program was undefining AF_NETLINK and thereby breaking AF_ROUTE...
* move all limits that don't vary out of bits/limits.h, into main limits.hRich Felker2011-06-251-27/+1
|
* use compiler builtins for variadic macros when availableRich Felker2011-04-271-1/+0
| | | | | | | | | | | this slightly cuts down on the degree musl "fights with" gcc, but more importantly, it fixes a critical bug when gcc inlines a variadic function and optimizes out the variadic arguments due to noticing that they were "not used" (by __builtin_va_arg). we leave the old code in place if __GNUC__ >= 3 is false; it seems like it might be necessary at least for tinycc support and perhaps if anyone ever gets around to fixing gcc 2.95.3 enough to make it work..
* move wait.h macros out of bits. they do not vary.Rich Felker2011-04-212-23/+0
|
* namespace fixes for sys/mman.hRich Felker2011-04-201-15/+15
|
* add syscall wrappers for posix_fadvise, posix_fallocateRich Felker2011-04-201-0/+2
|
* overhaul pthread cancellationRich Felker2011-04-171-1/+2
| | | | | | | | | | | | | | | | | | | | | | this patch improves the correctness, simplicity, and size of cancellation-related code. modulo any small errors, it should now be completely conformant, safe, and resource-leak free. the notion of entering and exiting cancellation-point context has been completely eliminated and replaced with alternative syscall assembly code for cancellable syscalls. the assembly is responsible for setting up execution context information (stack pointer and address of the syscall instruction) which the cancellation signal handler can use to determine whether the interrupted code was in a cancellable state. these changes eliminate race conditions in the previous generation of cancellation handling code (whereby a cancellation request received just prior to the syscall would not be processed, leaving the syscall to block, potentially indefinitely), and remedy an issue where non-cancellable syscalls made from signal handlers became cancellable if the signal handler interrupted a cancellation point. x86_64 asm is untested and may need a second try to get it right.
* fix O_SYNC definition, cleanup fcntl.hRich Felker2011-04-141-11/+5
|
* fix FAPPEND typo on x86_64 (previously only fixed on i386)Rich Felker2011-04-141-1/+1
|
* fcntl.h: move macros that do not vary between archs out of bitsRich Felker2011-04-141-24/+0
|
* fix broken fcntl locks on x86_64Rich Felker2011-04-141-3/+3
|
* numerous fixes to sysv ipcRich Felker2011-04-133-24/+15
| | | | | | | | | | some of these definitions were just plain wrong, others based on outdated ancient "non-64" versions of the kernel interface. as much as possible has now been moved out of bits/* these changes break abi (the old abi for these functions was wrong), but since they were not working anyway it can hardly matter.
* fix and cleanup suseconds_t/timeval stuff (broken on 64-bit)Rich Felker2011-04-131-1/+1
| | | | | trash in the upper 32 bits was making the kernel sleep forever in select on 64-bit systems.
* more types cleanupRich Felker2011-04-111-3/+0
| | | | | | | | the basic idea is that the only things in alltypes.h should be types that either vary from system to system (in practice, not just in theoretical la-la land - this is the implementation so we choose what constraints we want to impose on ports) or which are needed by multiple system headers.
* cleanup types stuff in headers, fix missing u_int*_t in sys/types.hRich Felker2011-04-111-11/+0
|
* add missing float.h macrosRich Felker2011-04-101-0/+3
| | | | | | actually FLT_ROUNDS needs to expand to a static inline function that obtains the current rounding mode and returns it, but that will be added later with fenv.h stuff.
* workaround broken msghdr struct on 64bit linuxRich Felker2011-04-081-2/+2
| | | | | | | | | | | POSIX clearly specifies the type of msg_iovlen and msg_controllen, and Linux ignores it and makes them both size_t instead. to work around this we add padding (instead of just using the wrong types like glibc does), but we also need to patch-up the struct before passing it to the kernel in case the caller did not zero-fill it. if i could trust the kernel to just ignore the upper 32 bits, this would not be necessary, but i don't think it will ignore them...
* add ip6 pktinfo stuff for x86_64Rich Felker2011-04-051-0/+12
| | | | these defs should probably all be moved out of bits and unified...
* uncomment IP_PKTINFORich Felker2011-04-051-1/+1
| | | | | this was a hack leftover from testing before the initial check-in to git.
* fix statvfs syscalls (missing size argument)Rich Felker2011-04-031-1/+1
|
* remove obsolete and useless useconds_t typeRich Felker2011-04-011-1/+0
|
* somehow timespec tv_nsec had the wrong type on x86_64... fixedRich Felker2011-04-011-1/+1
|
* avoid all malloc/free in timer creation/destructionRich Felker2011-03-301-1/+1
| | | | | | | | | | instead of allocating a userspace structure for signal-based timers, simply use the kernel timer id. we use the fact that thread pointers will always be zero in the low bit (actually more) to encode integer timerid values as pointers. also, this change ensures that the timer_destroy syscall has completed before the library timer_destroy function returns, in case it matters.
* some preliminaries for adding POSIX timersRich Felker2011-03-291-1/+1
|
* fix typo in x86_64 part of syscall overhaulRich Felker2011-03-191-1/+1
|
* syscall overhaul part two - unify public and internal syscall interfaceRich Felker2011-03-192-2/+69
| | | | | | | | | | | | | | | | with this patch, the syscallN() functions are no longer needed; a variadic syscall() macro allows syscalls with anywhere from 0 to 6 arguments to be made with a single macro name. also, manually casting each non-integer argument with (long) is no longer necessary; the casts are hidden in the macros. some source files which depended on being able to define the old macro SYSCALL_RETURNS_ERRNO have been modified to directly use __syscall() instead of syscall(). references to SYSCALL_SIGSET_SIZE and SYSCALL_LL have also been changed. x86_64 has not been tested, and may need a follow-up commit to fix any minor bugs/oversights.
* overhaul syscall interfaceRich Felker2011-03-191-0/+631
| | | | | | | | | | | | | | | this commit shuffles around the location of syscall definitions so that we can make a syscall() library function with both SYS_* and __NR_* style syscall names available to user applications, provides the syscall() library function, and optimizes the code that performs the actual inline syscalls in the library itself. previously on i386 when built as PIC (shared library), syscalls were incurring bus lock (lock prefix) overhead at entry and exit, due to the way the ebx register was being loaded (xchg instruction with a memory operand). now the xchg takes place between two registers. further cleanup to arch/$(ARCH)/syscall.h is planned.
* various legacy and linux-specific stuffRich Felker2011-03-181-0/+1
| | | | | this commit is part of an effort to make more of busybox work out-of-the-box.
* match dimensions so we can use all slots without invoking OOB-array-accessRich Felker2011-03-111-5/+5
|
* fix missing ENOTSUP error codeRich Felker2011-03-111-0/+1
|
* make sigaltstack work (missing macros in signal.h, error conditions)Rich Felker2011-03-101-0/+2
|
* fill in some missing siginfo stuff in signal.hRich Felker2011-02-201-5/+56
|
* add missing WIFCONTINUED macro and improve WIFSIGNALEDRich Felker2011-02-191-1/+2
|
* support the ugly and deprecated ucontext and sigcontext header stuff...Rich Felker2011-02-181-0/+32
| | | | | | | | | | | | | | only the structures, not the functions from ucontext.h, are supported at this point. the main goal of this commit is to make modern gcc with dwarf2 unwinding build without errors. honestly, it probably doesn't matter how we define these as long as they have members with the right names to prevent errors while compiling libgcc. the only time they will be used is for propagating exceptions across signal-handler boundaries, which invokes undefined behavior anyway. but as-is, they're probably correct and may be useful to various low-level applications dealing with virtualization, jit code generation, and so on...