uClibc-alpine/libc/stdio, branch master Where we track our uclibc patches tmpnam, tempnam are obsolete in SUSV4 2012-01-29T17:31:16+00:00 Bernhard Reutner-Fischer rep.dot.nop@gmail.com 2012-01-29T16:48:54+00:00 7c721d31e4b7a0bdf6f803b8e7c38996bf60b59f Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> 
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
stdio: add support for "e" flag with fopen() 2011-11-20T07:47:50+00:00 Mike Frysinger vapier@gentoo.org 2011-07-19T20:05:52+00:00 117a32a63b837730cc97b0a233ab46e9abc6c7a7 Support this useful glibc extension for optionally setting O_CLOEXEC on fopen streams. Signed-off-by: Mike Frysinger <vapier@gentoo.org> 
Support this useful glibc extension for optionally setting O_CLOEXEC
on fopen streams.

Signed-off-by: Mike Frysinger <vapier@gentoo.org>
stdio: hide _stdio_validate_FILE 2011-11-17T10:33:35+00:00 Bernhard Reutner-Fischer rep.dot.nop@gmail.com 2011-11-17T10:33:35+00:00 1ea3c5e6f11b91466546020f4e9ec13d1ab81be3 Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> 
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
libc: add missing lock initialization in vswprintf 2011-06-29T09:34:38+00:00 Maksim Rayskiy mrayskiy@broadcom.com 2011-06-17T01:14:01+00:00 18bf00f3123707f9d1d7a2876121dea1c2c39a89 Unlike vsnprintf, vswprintf does not properly initialize locking elements of FILE structure, which in some unfortunate cases can result in lockups in _vfwprintf_internal. Interesting, the initialization code was removed in 2a915734a32c5aec9a6a76c13bcb074d30e64171 at the same time as it was added to vsnprintf. Signed-off-by: Maksim Rayskiy <mrayskiy@broadcom.com> Signed-off-by: Carmelo Amoroso <carmelo.amoroso@st.com> 
Unlike vsnprintf, vswprintf does not properly initialize locking
elements of FILE structure, which in some unfortunate cases can result
in lockups in _vfwprintf_internal.
Interesting, the initialization code was removed in
2a915734a32c5aec9a6a76c13bcb074d30e64171 at the same time as it was added
to vsnprintf.

Signed-off-by: Maksim Rayskiy <mrayskiy@broadcom.com>
Signed-off-by: Carmelo Amoroso <carmelo.amoroso@st.com>
remove unused hidden functions 2011-03-09T22:20:16+00:00 Peter S. Mazinger ps.m@gmx.net 2011-03-09T22:20:16+00:00 abd6c6c29f82ddcc7c86c67519b79d2381622ed9 Signed-off-by: Peter S. Mazinger <ps.m@gmx.net> 
Signed-off-by: Peter S. Mazinger <ps.m@gmx.net>
make parse_printf_format() depend on UCLIBC_HAS_GLIBC_CUSTOM_PRINTF 2011-03-03T17:22:50+00:00 Peter S. Mazinger ps.m@gmx.net 2011-03-02T14:31:00+00:00 8116ca7baec0ff8c9bc35a2920aa36549e6004a4 we already remove the printf.h header if this option is disabled Signed-off-by: Peter S. Mazinger <ps.m@gmx.net> 
we already remove the printf.h header if this option is disabled

Signed-off-by: Peter S. Mazinger <ps.m@gmx.net>
*printf: Violation of precision with null string 2011-02-09T19:17:28+00:00 Jones Desougi jones.desougi@27m.se 2010-06-10T13:04:51+00:00 9a9a6365d5c5abb0fe3ec6cc09542e9c7e1d3bec When a string format is processed and the argument is NULL, this yields "(null)" regardless of precision. This does not make sense, precision should not be exceeded. A simple test shows that glibc outputs nothing if precision is smaller than six and the attached patch implements this same behaviour. Consider the not uncommon case of strings implemented like this: struct string { int len; char *ptr; }; There is often no nultermination and they may be printed like this: printf("%.*s", string.len, string.ptr); If len is 0 then ptr may be anything, but NULL is a common value. Obviously the empty string would be expected, not "(null)". Signed-off-by: Jones Desougi <jones.desougi@27m.se> Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> 
When a string format is processed and the argument is NULL, this yields
"(null)" regardless of precision. This does not make sense, precision
should not be exceeded. A simple test shows that glibc outputs nothing
if precision is smaller than six and the attached patch implements this
same behaviour.

Consider the not uncommon case of strings implemented like this:
struct string { int len; char *ptr; };
There is often no nultermination and they may be printed like this:
printf("%.*s", string.len, string.ptr);
If len is 0 then ptr may be anything, but NULL is a common value.
Obviously the empty string would be expected, not "(null)".

Signed-off-by: Jones Desougi <jones.desougi@27m.se>
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
stdio: fix diagnostic message 2011-01-21T08:16:51+00:00 Bernhard Reutner-Fischer rep.dot.nop@gmail.com 2011-01-20T08:15:21+00:00 a7c33ecabcead542e54c0c3514a92f4155add5b6 harmless copy'n paste error in #error Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> 
harmless copy'n paste error in #error

Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
__psfs_parse_spec: always use long int for %p 2011-01-11T18:47:58+00:00 Bernhard Reutner-Fischer rep.dot.nop@gmail.com 2011-01-11T18:46:56+00:00 e0d2b8e59beba49d6c2bdcf24257cc1834ce2b26 closes bug #3037 Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> 
closes bug #3037
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
vfprintf.c: reduce a chunk of #ifdef forest and remove one goto inside it 2010-10-19T13:07:00+00:00 Denys Vlasenko dvlasenk@redhat.com 2010-10-19T13:07:00+00:00 71dcf8f4401b27f2b7446601a6d0dbcddc0aa8b4 No code changes according to objdump. Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com> 
No code changes according to objdump.

Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>