From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: glibc_malloc_overhead
Date: Fri, 30 Sep 2011 20:21:34 +0300 [thread overview]
Message-ID: <83sjnec5ep.fsf@gnu.org> (raw)
In-Reply-To: <4E85F8B6.4090209@cs.ucla.edu>
> Date: Fri, 30 Sep 2011 10:13:26 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: emacs-devel@gnu.org
>
> > I'd suggest to only account for this overhead if glibc is
> > being used.
>
> Better yet, let's modify it to not depend on this particular glibc
> internal at all. I did that in the trunk, as bzr 105968.
Thanks.
prev parent reply other threads:[~2011-09-30 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 7:34 glibc_malloc_overhead Eli Zaretskii
2011-09-30 17:13 ` glibc_malloc_overhead Paul Eggert
2011-09-30 17:21 ` Eli Zaretskii [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=83sjnec5ep.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.