From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Better fix for ifaddrs
Date: Thu, 15 Mar 2007 00:45:00 -0000 [thread overview]
Message-ID: <45F8971B.9080708@redhat.com> (raw)
In-Reply-To: <20070314182000.GK1826@sunsite.mff.cuni.cz>
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
Jakub Jelinek wrote:
> if you think I should use
> __libc_use_alloca even for this, please let me know.
I fear for archs like ia64 and ppc64 where the page size can widely vary
we need this. But I think that this code should be optional, i.e., only
for those archs. No need to slow down the rest of the world.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2007-03-15 0:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 18:16 Jakub Jelinek
2007-03-15 0:45 ` Ulrich Drepper [this message]
2007-03-15 8:37 ` Jakub Jelinek
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=45F8971B.9080708@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).