From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix printf_unknown and do_positional (BZ #4514)
Date: Mon, 21 May 2007 18:08:00 -0000 [thread overview]
Message-ID: <4651E00A.2080903@redhat.com> (raw)
In-Reply-To: <20070521131923.GD3081@sunsite.mff.cuni.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I applied the patch.
> Also, wonder if we shouldn't compute the sum of allocaed memory sizes
> within whole *printf and use it for __libc_use_alloca instead of testing
> sizes separately. Or don't throw away the so far largest work buffer
> allocated through alloca, but instead reuse it if it is big enough.
Ideally this should be done, yes.
- --
⧠Ulrich Drepper ⧠Red Hat, Inc. ⧠444 Castro St ⧠Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGUeAK2ijCOnn/RHQRAjilAJ4/tWVxXpZU1pVRYRPEqgZLjwtQlwCfVgHY
3XtNcjy0LrQj4zfvd753vgs=
=cXDn
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2007-05-21 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 13:17 Jakub Jelinek
2007-05-21 18:08 ` Ulrich Drepper [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=4651E00A.2080903@redhat.com \
--to=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/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).