- 07 9月, 2012 4 次提交
-
-
由 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.
-
由 Rich Felker 提交于
unlike the memmove commit, this one should be fine to leave in place. wmemmove is not performance-critical, and even if it were, it's already copying whole 32-bit words at a time instead of bytes.
-
由 Rich Felker 提交于
this commit introduces a performance regression in many uses of memmove, which will need to be addressed before the next release. i'm making it as a temporary measure so that the restrict patch can be committed without invoking undefined behavior when memmove calls memcpy with overlapping regions.
-
由 Rich Felker 提交于
-
- 30 8月, 2012 4 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
all of the limits could use review, but err on the side of avoiding excessive rounds for now.
-
由 Rich Felker 提交于
these limits could definitely use review, but for now, i feel consistency and erring on the side of preventing servers from getting bogged down by excessively-slow user-provided settings (think .htpasswd) are the best policy. blowfish should be updated to match.
-
由 Rich Felker 提交于
based on versions sent to the list by nsz, with some simplification and debloating. i'd still like to get them a bit smaller, or ideally merge them into a single file with most of the code being shared, but that can be done later.
-
- 27 8月, 2012 2 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
based on patches submitted by boris brezillon. this commit also fixes the issue whereby the main application and libc don't have the address ranges of their mappings stored, which was theoretically a problem for RTLD_NEXT support in dlsym; it didn't actually matter because libc never calls dlsym, and it seemed to be doing the right thing (by chance) for symbols in the main program as well.
-
- 26 8月, 2012 7 次提交
-
-
由 Rich Felker 提交于
based on Gregor's patch sent to the list. includes: - stdalign.h - removing gets in C11 mode - adding aligned_alloc and adjusting other functions to use it - adding 'x' flag to fopen for exclusive mode
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
wrong hash was being passed; just a copy/paste error. did not affect lookups in the global namespace; this is probably why it was not caught in testing.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
previously, this usage could lead to a crash if the thread pointer was still uninitialized, and otherwise would just cause the canary to be zero (less secure).
-
由 Rich Felker 提交于
based on the patches contributed by boris brezillon.
-
- 24 8月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 20 8月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 19 8月, 2012 1 次提交
-
-
由 Rich Felker 提交于
before, only the first library that failed to load or symbol that failed to resolve was reported, and then the dynamic linker immediately exited. when attempting to fix a library compatibility issue, this is about the worst possible behavior. now we print all errors as they occur and exit at the very end if errors were encountered.
-
- 18 8月, 2012 3 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
if new shared mappings of files/devices/shared memory can be made between the time a robust mutex is unlocked and its subsequent removal from the pending slot in the robustlist header, the kernel can inadvertently corrupt data in the newly-mapped pages when the process terminates. i am fixing the bug by using the same global vm lock mechanism that was used to fix the race condition with unmapping barriers after pthread_barrier_wait returns.
-
由 Rich Felker 提交于
this affects at least the case of very long inputs, but may also affect shorter inputs that become long due to growth while upscaling. basically, the logic for the circular buffer indices of the initial base-10^9 digit and the slot one past the final digit, and for simplicity of the loop logic, assumes an invariant that they're not equal. the upscale loop, which can increase the length of the base-10^9 representation, attempted to preserve this invariant, but was actually only ensuring that the end index did not loop around past the start index, not that the two never become equal. the main (only?) effect of this bug was that subsequent logic treats the excessively long number as having no digits, leading to junk results.
-
- 16 8月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 15 8月, 2012 1 次提交
-
-
由 Rich Felker 提交于
not sure why these were originally omitted..
-
- 14 8月, 2012 2 次提交
-
-
由 Rich Felker 提交于
this function never existed historically; since the float/double functions it's based on are nonstandard and deprecated, there's really no justification for its existence except that glibc has it. it can be added back if there's ever really a need...
-
由 Rich Felker 提交于
-
- 12 8月, 2012 4 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
since this interface is rarely used, it's probably best to lean towards keeping code size down anyway. one-character needles will still be found immediately by the initial wcschr call anyway.
-
由 Rich Felker 提交于
optimized to avoid allocation and return lines directly out of the stream buffer whenever possible.
-
- 11 8月, 2012 2 次提交
-
-
由 Rich Felker 提交于
the strspn call was made for every format specifier and end-of-string, even though the expected return value was 1-2 for normal usage. replace with simple loop.
-
由 Rich Felker 提交于
amusingly, this cuts more than 10% off the run time of printf("a"); on the machine i tested it on. sadly the same optimization is not possible for snprintf without duplicating all the pseudo-FILE setup code, which is not worth it.
-
- 10 8月, 2012 3 次提交
-
-
由 Rich Felker 提交于
there are still some discussions going on about tweaking the code, but at least thing brings us to the point of having something working in the repository. hopefully the remaining major hashes (md5,sha) will follow soon.
-
由 Rich Felker 提交于
some minor changes to how hard-coded sets for thread-related purposes are handled were also needed, since the old object sizes were not necessarily sufficient. things have gotten a bit ugly in this area, and i think a cleanup is in order at some point, but for now the goal is just to get the code working on all supported archs including mips, which was badly broken by linux rejecting syscalls with the wrong sigset_t size.
-
由 Rich Felker 提交于
unfortunately, a large portion of programs which call crypt are not prepared for its failure and do not check that the return value is non-null before using it. thus, always "succeeding" but giving an unmatchable hash is reportedly a better behavior than failing on error. it was suggested that we could do this the same way as other implementations and put the null-to-unmatchable translation in the wrapper rather than the individual crypt modules like crypt_des, but when i tried to do it, i found it was making the logic in __crypt_r for keeping track of which hash type we're working with and whether it succeeded or failed much more complex, and potentially error-prone. the way i'm doing it now seems to have essentially zero cost, anyway.
-
- 09 8月, 2012 1 次提交
-
-
由 nsz 提交于
exp(inf), exp(-inf), exp(nan) used to raise wrong flags
-
- 08 8月, 2012 1 次提交
-
-
由 Rich Felker 提交于
-
- 06 8月, 2012 2 次提交
-
-
由 Rich Felker 提交于
untested
-
由 Rich Felker 提交于
-