- 18 4月, 2012 12 次提交
-
-
由 Rich Felker 提交于
this was basically harmless, but could have resulted in misreading inputs with more than a few gigabytes worth of digits..
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
this also includes a related fix for vswscanf's read function, which was returning a spurious (uninitialized) character for empty strings.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
this code worked in strtod, but not in scanf. more evidence that i should design a better interface for discarding multiple tail characters than just calling unget repeatedly...
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
at this point, strto* and all scanf family functions are using the new unified integer and floating point parser/converter code. the wide scanf is largely a wrapper for ordinary byte-based scanf; since numbers can only contain ascii characters, only strings need to be handled specially.
-
由 Rich Felker 提交于
-
- 17 4月, 2012 12 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
assuming other code is correct, this should be a no-op, but better to be safe...
-
由 Rich Felker 提交于
vfprintf temporarily swaps in a local buffer (for the duration of the operation) when the target stream is unbuffered; this both simplifies the implementation of functions like dprintf (they don't need their own buffers) and eliminates the pathologically bad performance of writing the formatted output with one or more write syscalls per formatting field. in cases like dprintf where we are dealing with a virgin FILE structure, everything worked correctly. however for long-lived files (like stderr), it's possible that the buffer bounds were already set for the internal zero-size buffer. on the next write, __stdio_write would pick up and use the new buffer provided by vfprintf, but the bound (wend) field was still pointing at the internal zero-size buffer's end. this in turn allowed unbounded writes to the temporary buffer.
-
由 Rich Felker 提交于
the l prefix is redundant/no-op with printf, since default promotions always promote floats to double; however, it is valid, and printf was wrongly rejecting it.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
not heavily tested but these functions appear to work correctly
-
由 Rich Felker 提交于
shunget cannot unget eof status, causing wcstol to leave endptr pointing to the wrong place when scanning, for example, L"0x". cheap fix is to make the read function provide an infinite stream of bogus characters rather than eof. really this is something of a design flaw in how the shgetc system is used for strto* and wcsto*; in the long term, I believe multi-character unget should be scrapped and replaced with a function that can subtract from the f->shcnt counter.
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
advantages over the old code: - correct results for floating point (old code was bogus) - wide/regular scanf separated so scanf does not pull in wide code - well-defined behavior on integers that overflow dest type - support for %[a-b] ranges with %[ (impl-defined by widely used) - no intermediate conversion of fmt string to wide string - cleaner, easier to share code with strto* functions - better standards conformance for corner cases the old code remains in the source tree, as the wide versions of the scanf-family functions are still using it. it will be removed when no longer needed.
-
由 Rich Felker 提交于
this is needed for upcoming new scanf
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
I'm not sure if it's legal for wordexp to modify this field, but this is the only easy/straightforward fix, and applications should not care. if it's an issue, i can work out a different (but more complex) solution later.
-
- 16 4月, 2012 4 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
this off-by-one error was causing values with just one digit past the decimal point to be treated by the integer case. in many cases it would yield the correct result, but if expressions are evaluated in excess precision, double rounding may occur.
-
由 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
-
- 15 4月, 2012 1 次提交
-
-
由 Rich Felker 提交于
the "< 0" test was always false due to use of an unsigned type. this resulted in infinite loops on 32-bit machines (adding -1U to a pointer is the same as adding -1) and crashes on 64-bit machines (offsetting the string pointer by 4gb-1b when an illegal sequence was hit).
-
- 14 4月, 2012 3 次提交
-
-
由 Rich Felker 提交于
this is legal since sa_* is in the reserved namespace for signal.h, per posix. note that the sa_restorer field is not used anywhere, so programs that are trying to use it may still break, but at least they'll compile. if it turns out such programs actually need to be able to set their own sa_restorer to function properly, i'll add the necessary code to sigaction.c later.
-
由 Rich Felker 提交于
TRE wants to treat + and ? after a +, ?, or * as special; ? means ungreedy and + is reserved for future use. however, this is non-conformant. although redundant, these redundant characters have well-defined (no-op) meaning for POSIX ERE, and are actually _literal_ characters (which TRE is wrongly ignoring) in POSIX BRE mode. the simplest fix is to simply remove the unneeded nonstandard functionality. as a plus, this shaves off a small amount of bloat.
-
由 Rich Felker 提交于
-
- 13 4月, 2012 3 次提交
-
-
由 Rich Felker 提交于
this increases code size slightly, but it's considerably faster, especially for power-of-2 bases.
-
由 Rich Felker 提交于
at -Os optimization level, gcc refuses to inline these functions even though the inlined code would roughly the same size as the function call, and much faster. the easy solution is to make them into macros.
-
由 Rich Felker 提交于
whenever the base was small enough that more than one digit could still fit after UINTMAX_MAX/36-1 was reached, only the first would be allowed; subsequent digits would trigger spurious overflow, making it impossible to read the largest values in low bases.
-
- 12 4月, 2012 5 次提交
-
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-
由 Rich Felker 提交于
-