From: Segher Boessenkool <segher@koffie.nl>
To: Bruce Korb <bkorb@veritas.com>
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>,
bug-glibc@gnu.org, schwab@suse.de,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: BUG: printf formatting libc.so.6
Date: Thu, 29 May 2003 17:20:00 -0000 [thread overview]
Message-ID: <3ED3695F.4080908@koffie.nl> (raw)
In-Reply-To: <3ED266D7.DA658597@veritas.com>
>>void main(void) { printf("%1$d %1$c %2$d %2$c\n", 32, 49); }
This fails on ancient glibc's, with ancient gcc's, too.
The failure mode is more apparent on big-endian systems.
See union printf_arg and how it's used in vfprintf.c .
The fix is probably to document not to use a positional
parameter more than once.
Segher
prev parent reply other threads:[~2003-05-29 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2A0007B587D@vcnet.vc.cvut.cz>
2003-05-26 19:23 ` Bruce Korb
2003-05-27 0:05 ` Jakub Jelinek
2003-05-29 17:20 ` Segher Boessenkool [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ED3695F.4080908@koffie.nl \
--to=segher@koffie.nl \
--cc=VANDROVE@vc.cvut.cz \
--cc=bkorb@veritas.com \
--cc=bug-glibc@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).