public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neleai at seznam dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/14483] obstack uses int for allocation sizes
Date: Sun, 20 Oct 2013 21:08:00 -0000 [thread overview]
Message-ID: <bug-14483-131-wOFELgvyB1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14483-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14483
Ondrej Bilka <neleai at seznam dot cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |neleai at seznam dot cz
Severity|normal |enhancement
--- Comment #2 from Ondrej Bilka <neleai at seznam dot cz> ---
Returning a stack sie as size_t could be feasible. However extending arguments
from ints is nonsense, obstack is used for quick allocation of lot of small
objects. You can have only few large objects until you run out of memory, Also
returning huge chunks of memory to system looks better than keeping them in
obstack.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-20 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 22:23 [Bug malloc/14483] New: " jsm28 at gcc dot gnu.org
2013-01-09 16:52 ` [Bug malloc/14483] " schwab@linux-m68k.org
2013-10-20 21:08 ` neleai at seznam dot cz [this message]
2014-06-17 18:36 ` fweimer at redhat dot com
2014-06-25 10:49 ` fweimer at redhat dot com
2014-07-24 7:01 ` amodra at gmail dot com
2014-08-04 11:19 ` fweimer at redhat dot com
2014-12-10 13:02 ` amodra at gmail dot com
2024-04-24 7:04 ` amodra at gmail dot com
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=bug-14483-131-wOFELgvyB1@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).