From: Andreas Schwab <schwab@redhat.com>
To: libc-hacker@sourceware.org
Subject: [PATCH] Remove __libc_alloca_cutoff workaround
Date: Thu, 19 May 2011 11:48:00 -0000 [thread overview]
Message-ID: <m3mxiioqrg.fsf@redhat.com> (raw)
Since __libc_alloca_cutoff is now exported it is no longer need to
override __libc_use_alloca for nscd.
Andreas.
2011-05-19 Andreas Schwab <schwab@redhat.com>
* grp/compat-initgroups.c (__libc_use_alloca): Don't define.
---
grp/compat-initgroups.c | 6 ------
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/grp/compat-initgroups.c b/grp/compat-initgroups.c
index 7bcc203..260c482 100644
--- a/grp/compat-initgroups.c
+++ b/grp/compat-initgroups.c
@@ -8,12 +8,6 @@ typedef enum nss_status (*end_function) (void);
typedef enum nss_status (*get_function) (struct group *, char *,
size_t, int *);
-/* This file is also used in nscd where __libc_alloca_cutoff is not
- available. */
-#ifdef NOT_IN_libc
-# define __libc_use_alloca(size) ((size) < __MAX_ALLOCA_CUTOFF * 4)
-#endif
-
static enum nss_status
compat_call (service_user *nip, const char *user, gid_t group, long int *start,
--
1.7.4.4
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
reply other threads:[~2011-05-19 11:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3mxiioqrg.fsf@redhat.com \
--to=schwab@redhat.com \
--cc=libc-hacker@sourceware.org \
/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).