- 30 4月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 27 4月, 2012 1 次提交
-
-
由 Rich Felker 提交于
if the compiler provides a value, use it; otherwise fallback to the platform default (2).
-
- 25 4月, 2012 1 次提交
-
-
由 Rich Felker 提交于
otherwise this BADLY breaks if -funsigned-char is passed to gcc
-
- 16 4月, 2012 2 次提交
-
-
由 Rich Felker 提交于
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.
-
由 Rich Felker 提交于
F_* is in the reserved namespace so no feature test is needed
-
- 04 4月, 2012 1 次提交
-
-
由 Rich Felker 提交于
when the "r" (register) constraint is used to let gcc choose a register, gcc will sometimes assign the same register that was used for one of the other fixed-register operands, if it knows the values are the same. one common case is multiple zero arguments to a syscall. this horribly breaks the intended usage, which is swapping the GOT pointer from ebx into the temp register and back to perform the syscall. presumably there is a way to fix this with advanced usage of register constaints on the inline asm, but having bad memories about hellish compatibility issues with different gcc versions, for the time being i'm just going to hard-code specific registers to be used. this may hurt the compiler's ability to optimize, but it will fix serious miscompilation issues. so far the only function i know what compiled incorrectly is getrlimit.c, and naturally the bug only applies to shared (PIC) builds, but it may be more extensive and may have gone undetected..
-
- 22 3月, 2012 1 次提交
-
-
由 Rich Felker 提交于
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.
-
- 25 2月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 16 2月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 09 2月, 2012 1 次提交
-
-
由 Rich Felker 提交于
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.
-
- 21 1月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 18 10月, 2011 1 次提交
-
-
由 Rich Felker 提交于
patches by sh4rm4, presumably needed to make gdb or some similar junk happy...
-
- 15 10月, 2011 1 次提交
-
-
由 Rich Felker 提交于
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.
-
- 05 10月, 2011 1 次提交
-
-
由 Rich Felker 提交于
no idea why these 4 are permuted and the rest are standard/generic
-
- 01 10月, 2011 3 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
- 23 9月, 2011 4 次提交
-
-
由 Rich Felker 提交于
actually this is just to avoid gcc being stupid and refusing to inline the function version, even when the size cost is essentially identical whether it's inlined or not.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
- 22 9月, 2011 1 次提交
-
-
由 Rich Felker 提交于
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.
-
- 20 9月, 2011 4 次提交
-
-
由 Rich Felker 提交于
at the same time, make struct statfs match the traditional definition and make it more useful, especially the fsid_t stuff.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
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.
-
由 Rich Felker 提交于
this was the cause of crashes in printf when attempting to print floating point values.
-
- 19 9月, 2011 4 次提交
-
-
由 Rich Felker 提交于
this port assumes eabi calling conventions, eabi linux syscall convention, and presence of the kernel helpers at 0xffff0f?0 needed for threads support. otherwise it makes very few assumptions, and the code should work even on armv4 without thumb support, as well as on systems with thumb interworking. the bits headers declare this a little endian system, but as far as i can tell the code should work equally well on big endian. some small details are probably broken; so far, testing has been limited to qemu/aboriginal linux.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
- 23 8月, 2011 1 次提交
-
-
由 Rich Felker 提交于
this behavior (opening fds 0-2 for a suid program) is explicitly allowed (but not required) by POSIX to protect badly-written suid programs from clobbering files they later open. this commit does add some cost in startup code, but the availability of auxv and the security flag will be useful elsewhere in the future. in particular auxv is needed for static-linked vdso support, which is still waiting to be committed (sorry nik!)
-
- 15 8月, 2011 1 次提交
-
-
由 Rich Felker 提交于
-
- 07 8月, 2011 1 次提交
-
-
由 Rich Felker 提交于
if gcc decided to move this across a conditional that checks validity of the thread register, an invalid thread-register-based read could be performed and raise sigsegv.
-
- 22 7月, 2011 1 次提交
-
-
由 Rich Felker 提交于
some program was undefining AF_NETLINK and thereby breaking AF_ROUTE...
-
- 26 6月, 2011 2 次提交
-
-
由 Rich Felker 提交于
1. search was wrongly beginning with lib itself rather than dso head 2. inconsistent resolution of function pointers for functions in plt
-
由 Rich Felker 提交于
-
- 25 6月, 2011 1 次提交
-
-
由 Rich Felker 提交于
first, use $LD_LIBRARY_PATH unless suid. if that fails, read path from /etc/ld-musl-$ARCH.path and fallback to a builtin default.
-
- 19 6月, 2011 1 次提交
-
-
由 Rich Felker 提交于
some notes: - library search path is hard coded - x86_64 code is untested and may not work - dlopen/dlsym is not yet implemented - relocations in read-only memory won't work
-
- 15 6月, 2011 1 次提交
-
-
由 Rich Felker 提交于
-
- 07 6月, 2011 1 次提交
-
-
由 Rich Felker 提交于
unfortunately traditional i386 practice was to use "long" rather than "int" for wchar_t, despite the latter being much more natural and logical. we followed this practice, but it seems some compilers (clang and maybe certain gcc builds or others too..?) have switched to using int, resulting in spurious pointer type mismatches when L"..." wide strings are used. the best solution I could find is to use the compiler's definition of wchar_t if it exists, and otherwise fallback to the traditional definition. there's no point in duplicating this approach on 64-bit archs, as their only 32-bit type is int.
-