From: "H . J . Lu" <hjl@valinux.com>
To: GNU C Library <libc-hacker@sourceware.cygnus.com>
Subject: A patch for linuxthreads
Date: Mon, 04 Sep 2000 10:48:00 -0000 [thread overview]
Message-ID: <20000904104812.A12853@valinux.com> (raw)
page_roundup is faster than roundup. Since `ps' is returned from
__getpagesize (), it should be ok.
--
H.J. Lu (hjl@gnu.org)
---
2000-09-04 H.J. Lu <hjl@gnu.org>
* attr.c (__pthread_attr_setguardsize): Use page_roundup
instead of roundup to round up to the page size.
Index: attr.c
===================================================================
RCS file: /work/cvs/gnu/glibc/linuxthreads/attr.c,v
retrieving revision 1.1.1.2
diff -u -p -r1.1.1.2 attr.c
--- attr.c 2000/08/16 00:55:46 1.1.1.2
+++ attr.c 2000/08/17 16:18:05
@@ -147,7 +147,7 @@ int __pthread_attr_setguardsize(pthread_
size_t ps = __getpagesize ();
/* First round up the guard size. */
- guardsize = roundup (guardsize, ps);
+ guardsize = page_roundup (guardsize, ps);
/* The guard size must not be larger than the stack itself */
if (guardsize >= attr->__stacksize) return EINVAL;
next reply other threads:[~2000-09-04 10:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-04 10:48 H . J . Lu [this message]
2000-09-04 19:54 ` Ulrich Drepper
-- strict thread matches above, loose matches on Subject: below --
1999-12-16 16:12 H . J . Lu
[not found] ` <199912170033.QAA01416@localhost.cygnus.com>
1999-12-16 16:43 ` H . J . Lu
1999-04-14 22:31 H.J. Lu
1999-04-14 23:51 ` Ulrich Drepper
1999-03-17 13:44 Mike Stump
1999-03-18 7:44 ` H.J. Lu
1999-03-16 20:28 H.J. Lu
1999-03-17 2:20 ` Mark Kettenis
1999-03-17 7:21 ` H.J. Lu
1999-03-17 4:52 ` Andrey Slepuhin
1998-12-02 10:35 H.J. Lu
1998-12-02 11:44 ` Ulrich Drepper
1998-10-24 18:33 H.J. Lu
1998-10-25 0:59 ` Ulrich Drepper
1998-10-25 8:22 ` H.J. Lu
1998-10-25 8:22 ` Ulrich Drepper
1998-08-08 23:26 H.J. Lu
1998-08-09 8:59 ` Ulrich Drepper
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=20000904104812.A12853@valinux.com \
--to=hjl@valinux.com \
--cc=libc-hacker@sourceware.cygnus.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).