unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: emacs-devel@gnu.org
Cc: "Ondřej Bílka" <neleai@seznam.cz>
Subject: Re: [RFC] Replacing malloc_get_state functionality.
Date: Mon, 24 Feb 2014 18:11:35 -0800	[thread overview]
Message-ID: <530BFBD7.2040606@cs.ucla.edu> (raw)
In-Reply-To: <530BDB13.5040601@dancol.org>

'./configure emacs_cv_var_doug_lea_malloc=no' works for me in the sense 
that I can do a 'make bootstrap' on Fedora 20 x86-64, and the resulting 
Emacs works interactively.  In this configuration Emacs supplies its own 
malloc so the performance is not quite as good (text 0.5% larger, data 
7.6% larger, 14% more CPU time on my usual benchmark) but I don't 
observe any bugs.

It's possible that there's a bigger problem here; but if so, wouldn't it 
the same bigger problem exist on non-glibc platforms already?  If so, 
any fix should also work on any future glibc platforms that lack 
malloc_get_state.

More generally, Emacs by itself should not inhibit glibc from making 
significant malloc performance improvements that would benefit a large 
set of programs.  If Emacs is the main reason these improvements aren't 
being made, then we should go ahead and make them, as we should be able 
to tweak Emacs to work well with the resulting system.



  reply	other threads:[~2014-02-25  2:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 23:29 [RFC] Replacing malloc_get_state functionality Ondřej Bílka
2014-02-21  7:38 ` Paul Eggert
2014-02-24 15:05   ` Ondřej Bílka
2014-02-24 15:31   ` Andreas Schwab
2014-02-24 20:01     ` Stefan Monnier
2014-02-24 23:51       ` Daniel Colascione
2014-02-25  2:11         ` Paul Eggert [this message]
2014-03-04 10:31         ` Ondřej Bílka

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=530BFBD7.2040606@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=neleai@seznam.cz \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).